Explore the tools built for a new civilization in the 2026 EVE Frontier Hackathon.
Voting has ended, but the project gallery remains open.
Explore the tools built for a new civilization in the 2026 EVE Frontier Hackathon.
Voting has ended, but the project gallery remains open.
🚀 Powerlay Frontier
Community desktop companion for EVE Frontier
production and mining planning
tribe coordination via contracts
transparent in-game overlays for mining, production timers, etc
available for Windows and macOS
Latest features and changes are in Releases
Some features (Contracts, Scout) interact with the SUI Network and require a connected EVE Wallet.
Why Powerlay?
EVE Frontier rewards coordination, but the game gives you almost no tools for it. Powerlay Frontier fills the gap: plan complex builds, track ore across mining runs, and keep your tribe in sync - all without leaving the game.
Features
🛠️ Builder - production & mining hub (stable)
Plan chains of production and break down ingredients for multiple builds at once. Builder is the core of Powerlay:
- Recipe breakdown - select what you want to build, see every ore and intermediate material you need, across the entire dependency tree.
- Real-time mining tracker - always know how much of each ore you've already mined and how much is left for your target builds.
- Run estimates - get quick estimates for required mining trips, refine your strategy on the fly, and avoid wasting time on wrong materials.
🖥️ Overlay - always-on-screen panels (stable)
Lightweight transparent panels that stay on top of EVE Frontier. See your production queue, ore counts, and tribe contracts without tabbing out. Designed to be unobtrusive - shows only what you need, when you need it.
📜 Contracts - tribe & public tasks (work in progress)
Create contracts tied to your EVE Wallet identity. Track progress, see who contributed what, and distribute rewards - replacing the spreadsheet chaos most tribes rely on today. Supports both tribe-only and public contracts. For solo pilots, public contracts are a way to take on tribe orders and earn ships or materials that would otherwise take much longer to unlock on your own.
🔭 Scout - system scanner (early prototype)
Scan and tag systems for tribe-oriented missions, mining hotspots, or upcoming targets. Currently in prototype stage - testing how players prefer to input and share system data, no backend yet.
## Designed for tribes, open to everyone
Powerlay is built around tribe workflows: shared storage, group contracts, and contribution tracking let your tribe coordinate resource drops, rewards, and shared goals without external tools.
Solo pilots still get full access to the core toolset - builder module, overlays, public contracts...
Safe, honest, community-focused
- No automation - Powerlay never plays the game for you.
- No memory reading, no process injection - it's a standalone window, completely separate from the EVE Frontier client.
- Wallet integration - connects to your EVE Wallet and public game data. That's it.
- Built by players - features are added based on real feedback from tribes and solo pilots.
---
Actively developed. Join us on Discord to share feedback and shape the roadmap.
A checkpoint-driven event scanner for the EVE Frontier package on the Sui blockchain. It polls for new checkpoints, drains all on-chain Move events across every watched module, parses them into typed Python dataclasses. It can also scan through chain history for events matching a filter.
Currently development environment running live on Stillness
The codebase includes three example usages of this concept.
Uses the event streamer to listen for the latest on-chain events. A WebHook server then allows consumers to subscribe to channels to then be streamed events. A web app acts as a web hook consumer and display events on a front-end.
Scans through events in order to populate a database. This additional data can then be used to produced enriched events. For example, 'CharacterCreatedEvent' and 'MetadataChangedEvent' can be scanned to produce a lookup table to resolve player id's to their names. This data can then be used to create more meaningful events, such as KillMails that include player names and tribe.
Uses the event streamer to listen for the latest on-chain events. On new events, the discord bot will notify a specified channel.
Frontier Periscope is an organizational toolkit for EVE Frontier built on the Sui testnet. It started as a monitoring tool but grew into something much bigger.
The core idea is to give non-technical players access to blockchain data and to offer enhanced features to smart assemblies like custom markets, standings-gated access, and shared treasuries.
You can create your own custom currencies and trade them through on-chain markets at any Smart Storage Unit. The market system uses atomic escrow transfers so items and payments move together in a single transaction, no trust required.
There's a standings and diplomacy system that lets you manage relationships with other players and tribes through on-chain registries. These standings feed into everything else, like controlling who can access your gates, trade at your SSUs, or even how your turrets pick targets. You can set up gate tolls in any custom currency and route the fees to a shared treasury wallet that multiple admins can manage.
Private encrypted maps let you share intel with your organization without exposing it to everyone on chain. The encryption is end-to-end so only invited members can see location data.
On the monitoring side, Sonar tracks real-time events from both the blockchain and local game logs. You get live notifications for combat, trades, fuel levels, gate activity, and structure changes. The 3D Star Map shows the full solar system with jump route planning.
Everything runs as a React app with an Eve Vault wallet connection. The smart contracts are all published on testnet and the dapp works directly with in-game smart assemblies through the EVE Frontier dapp framework.
The first trustless on-chain P2P marketplace for EVE Frontier, built on Sui.
Players list, buy, and cancel in-game items directly — no Discord middlemen, no scam risk. Built with two Move modules: trade_hub (core marketplace with 1% fee split via Coin<SUI>) and trade_terminal (Smart Assembly SSU bridge for register/sync/list in one atomic tx).
Key features:
• Browse all active listings with live on-chain data (auto-refreshes every 15s)
• One-click buy — 99% to seller, 1% platform fee, split atomically in Move
• Smart Terminal tab — register your EVE Frontier SSU, sync inventory on-chain, list directly through terminal
• Shared objects + capability pattern (AdminCap, TerminalCap) + on-chain events
Contracts deployed on Sui Devnet. 3/3 Move unit tests passing.
https://ef-plutarch.com
A full-featured dApp for managing EVE Frontier corporations on the Sui blockchain. Built with React 19, TypeScript, Vite, and SQLite.
Corporate Storage — Three-tier on-chain storage (ephemeral → open → main) with escrow management
Goal & Mission System — Create goals, decompose them into missions, assign to wings, track progress
Wing Management — Organise members into wings with role-based assignments, allocate resources and missions to them
Market Board — Tribal marketplace with buy/sell orders and partial fills
Contract System — Create and manage contracts with on-chain item escrow
Delivery System — Multi-courier delivery logistics with tracking
Network Map — Interactive map of SSU network with territory management
Tribe Credits — Deploy custom Sui coins for your tribe with on-chain vaults, reward your pilots and trade with other tribes
Analytics — Ledger tracking, budget management, and mission analytics
Territory Fuel — Monitor network node fuel levels across your territory
A decentralized insurance primitive for EVE Frontier tribes, built on Sui.
See it here! rift-mercantile.vercel.app
Maintaining fleet expensive. Loss expensive. Cover fleet using insurance. Less expensive.
What it is
RIFT MERCANTILE lets EVE Frontier tribes pool SUI, sell coverage policies to members, and automatically pay out when a covered pilot dies in space. It's an on-chain financial protection layer built specifically for EVE Frontier's player-driven economy turning the inevitable losses of exploration and combat into a manageable, trust-minimized risk.
How it works
A tribe leader deploys an insurance pool directly on Sui, deposits SUI as the reserve, and sets payout and premium amounts. Members registered to the pool can purchase a policy through the dApp. When they die in EVE Frontier, they file a claim, the dApp verifies their death against live Stillness chain data using suix_queryEvents, and if verified, the contract releases the payout automatically.
The Policy NFT
Every purchased policy mints a Policy NFT to the buyer's wallet, a real Sui object representing their coverage certificate. It contains the holder's address, pool ID, and a purchase timestamp anchored on-chain. When a claim is filed and verified, the contract consumes the NFT (burning it permanently) and transfers the payout. One claim per policy, enforced by the Move contract.
Built in Move on Sui
The core protocol is a Move smart contract deployed on Sui testnet. It manages pool state as a shared Sui object, enforces membership checks before policy purchase, mints Policy NFTs via transfer::transfer, and handles claim payouts via coin::take. Events are emitted for every action, PoolCreated, PolicyPurchased, ClaimPaid ,making the full audit trail queryable on-chain forever. The contract uses clock::timestamp_ms() for tamper-proof policy timestamps.
Token support
Today RIFT MERCANTILE uses SUI as the reserve and premium currency, pools are funded in SUI, premiums are paid in SUI, payouts are in SUI. The architecture is designed to extend to any Sui-native token: the pool's Coin<T> type parameter can be swapped to support EVE's native token or any future Frontier-native asset once available on Sui, making RIFT MERCANTILE a general-purpose insurance primitive for the entire ecosystem.
EVE Vault Integration
RIFT MERCANTILE connects natively with EVE Vault, CCP's official wallet, based on the Sui Wallet Standard. Players connect their EVE account directly. The dApp detects EVE Vault automatically on page load, then when a player chooses to execute coverage, the player is prompted to approve, and submits signed Programmable Transaction Blocks using the sui:signAndExecuteTransaction feature. Kill verification cross-references the connected wallet's on-chain character identity against live Stillness killmail events, tying the insurance claim directly to the player's in-game identity.
On-chain Construction
Every step of the protocol is verifiable on Suiscan testnet:
Contract: 0x0f31f8801c3b81f65f8dd0617aad7143411273ec11ea8f6ee7a9eae7d7e22b65
The RIFT MERCANTILE Move smart contract. All protocol logic lives here: create_pool, buy_policy, claim, add_member. Immutable once deployed. https://suiscan.xyz/testnet/object/0x0f31f8801c3b81f65f8dd0617aad7143411273ec11ea8f6ee7a9eae7d7e22b65
Live Pool (RIFT MERCANTILE ALPHA): 0x46299b5aab478290cea2261dfc1812c97276c810d4cbde9a3b01659362d88acc
The active insurance pool object on-chain. Shared Sui object holding the 0.5 SUI reserve, member list, and policy settings. Anyone can interact with it. https://suiscan.xyz/testnet/object/0x46299b5aab478290cea2261dfc1812c97276c810d4cbde9a3b01659362d88acc
Policy NFT (purchased via EVE Vault): 0x425493084fe057a6fa5b07cf6b6de2d6d7d5243ce83a3126e45becf95c365950
An NFT sitting in the EVE Vault wallet. Records holder address, pool ID, and purchase timestamp. Consumed permanently when a claim is filed and payout released. https://suiscan.xyz/testnet/object/0x425493084fe057a6fa5b07cf6b6de2d6d7d5243ce83a3126e45becf95c365950
Policy purchase tx: DpczbKhQHZaMncgGWSB8jjJwPh5jzjwKxziCnqB8EPjq
The Sui transaction where the Policy NFT was minted. Signed by EVE Vault via the dApp. Proves the full end-to-end flow: wallet connected → premium paid → NFT received. https://suiscan.xyz/testnet/tx/DpczbKhQHZaMncgGWSB8jjJwPh5jzjwKxziCnqB8EPjq
Stillness World Package: 0x28b497559d65ab320d9da4613bf2498d5946b2c0ae3597ccfda3072ce127448c
CCP's official EVE Frontier game contract on Sui testnet. Source of all in-game data — characters, killmails, assemblies, gate jumps. RIFT MERCANTILE reads killmail events from this package to verify deaths. https://suiscan.xyz/testnet/object/0x28b497559d65ab320d9da4613bf2498d5946b2c0ae3597ccfda3072ce127448c
Killmail Registry: 0x7fd9a32d0bbe7b1cfbb7140b1dd4312f54897de946c399edb21c3a12e52ce283
The on-chain object storing all Stillness killmail records. Every player death emits a KillmailCreatedEvent from here. RIFT MERCANTILE queries this to confirm a covered pilot died after their policy was purchased before releasing any payout. https://suiscan.xyz/testnet/object/0x7fd9a32d0bbe7b1cfbb7140b1dd4312f54897de946c399edb21c3a12e52ce283
Live: rift-mercantile.vercel.app
Notes
¹ Currency: SUI is used as the reserve and premium token for this submission because EVE Frontier's native in-game currencies (LUX/EVE tokens) are not yet available as Sui-native assets. The contract is architected as Coin<T> and will support native Frontier tokens when they become available on-chain.
² Kill verification dependency: Claim verification relies on killmail event data indexed from the Stillness chain via suix_queryEvents. The accuracy and latency of this data is dependent on CCP's on-chain event infrastructure. In the current testnet environment, killmail propagation can lag by minutes to hours.
³ Scope of submission: This submission demonstrates the technical possibility of decentralized tribe fleet insurance on Sui, not a production-ready financial product. The economic parameters (premium rates, payout ratios, pool sizing, actuarial modeling) are placeholders. The value being submitted is the protocol architecture, the Move contract, the EVE Vault integration pattern, and the proof that this class of financial primitive is buildable on EVE Frontier today.
Notes on the future:
In building this product, I notice that it was a primitive to more robust opportunities. Something I always considered was "Could we assign a risk rating, or credit rating, to a player, especially if they are paid to be a courier." And the answer to that viewpoint, I think, is one day.
There are some V2 concepts worth exploring based off this project that I didn't have the time to commit to, but should there be another hackathon, I would love to.
