Frequently Asked Questions

Frontier Pulse is a real-time civilization health monitor for EVE Frontier, treating the game universe as a living organism with vital signs. It combines a visualization layer (Pulse) with a trust intelligence engine (Agora) to answer whether civilization is genuinely thriving or just busy dying.

The External Tools track of the EVE Frontier x Sui Hackathon 2026. We connect via the World API rather than in-world Smart Assembly mods.

No. Frontier Pulse reads public data from the World API and Sui blockchain. You can explore the galaxy, analyze trust patterns, and monitor civilization health without a game account.

Yes. Systems, smart assemblies, and killmails come from the live EVE Frontier World API. When enrichment data isn’t available for a system, we use a deterministic hash function that generates consistent pseudo-random vitals per system ID.

Sui’s object-centric model, sub-second finality, and Programmable Transaction Blocks (PTBs) let us batch 50+ score updates into a single transaction. The shared object pattern (PulseRegistry) provides natural concurrency for reads while restricting writes to authorized oracles.

A Node.js service on a 10-minute cron cycle. Each cycle: (1) fetches all 24,502 systems from World API, (2) enriches with assemblies + killmails, (3) computes system health + player reputation + global CHI, (4) detects anomalies, (5) writes results on-chain via batched PTBs.

Yes. The frontend computes vitals locally using the same deterministic hash function. You lose on-chain persistence and trust scores, but the galaxy map, heartbeat, and system views all function standalone.

All nodes are drawn as simple Canvas circles with trust-based coloring. Performance comes from: depth-based sizing (no complex shapes), viewport culling (skip off-screen nodes), color batching, and an offscreen canvas cache for the static background layer.

Trust Level = 100 - (kill_ratio × 50) + infrastructure_boost. High combat relative to player count lowers trust; infrastructure investment raises it. The formula runs identically in the oracle (scoring.ts) and frontend (vitals.ts).

Archetypes are classified by dimension thresholds. A Civilization Builder has Stewardship ≥ 80 and Reliability ≥ 70 (they build for others). A Warlord has Volatility ≥ 70 and Commerce < 40 (high combat, little trade). First matching rule wins.

The oracle reads from the live World API, not player-submitted data. Scores reflect actual on-chain activity. The multi-dimensional approach (6 sub-indices) means boosting one metric doesn’t inflate the overall score — you’d need genuine broad-spectrum civilization health.

Pattern matching on system scores: Blackout (infrastructure exists but activity collapsed), Trust Collapse (active players but trust critically low), Combat Hotspot (extreme PvP), Trade Spike (unusual transaction volume).

No. The dashboard is fully functional without a wallet. Connecting a Sui wallet unlocks personalized features: your systems highlighted on the map, watchlist persistence, and the ability to endorse systems on-chain.

An endorsement is an on-chain signal from your wallet validating a system’s activity. It’s stored in the PulseRegistry with anti-spam deduplication (one endorsement per wallet per system via BCS key).

Any Sui-compatible wallet via @mysten/dapp-kit: Sui Wallet, Suiet, Ethos, Nightly, Martian. You can also enter a wallet address manually for read-only features.