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.
Every civilization begins with trade.
KARUM is an on-chain
marketplace registry for EVE Frontier where SSU owners register
their shops and players find, navigate to, and buy resources —
all in seconds.
Named after the Kārum, humanity's first organized trade network
built by Assyrian merchants in 1950 BC. 21 marketplace colonies,
every transaction on clay tablets. We rebuilt it on Sui.
What it does:
- SSU owners register shops on-chain — what they sell, at what price
- Players search, filter, and sort shops by resource, system, or stock
- Built-in navigation to fly directly to any shop
- Buy resources on-chain, trustless, instant
- Discord bot notifies your server when shops go live or items sell
- Zero fees. No coding knowledge needed. Open to everyone.
How it works:
KARUM combines an on-chain ShopRegistry (Sui Move smart contract)
with a React frontend that cross-references registry data with
live game state. The registry stores seller intent — the game
confirms reality. Together they give pilots a complete, real-time
picture of every marketplace in the Frontier.
Built with Sui Move, React, TypeScript.
Deployed on Sui.
Walrus Deployment:
Web:
PactaForge — Programmable Agreements with Verifiable Execution
PactaForge is an execution layer for programmable agreements built on Sui, demonstrated through real in-game economies like EVE Frontier.
Today, smart contracts primarily execute transactions, but real-world agreements depend on more than transfers — they require conditions, proofs, delivery verification, and dispute resolution. This critical context is often fragmented or trusted off-chain.
PactaForge solves this by combining on-chain agreement execution with verifiable data.
Each agreement is created as a programmable on-chain object where assets are locked trustlessly, and execution is triggered only when predefined, provable conditions are met.
We demonstrate this through three live contract flows:
• Bounty Contracts — rewards are locked and only released when a valid on-chain killmail proves completion
• Delivery Jobs — payments are automatically released when required items are delivered and verified on-chain
• Trade Escrow — atomic swaps where both parties lock assets and settlement is enforced without counterparty risk
All flows execute on Sui testnet using real wallets, real assets, and verifiable on-chain events.
By integrating verifiable data primitives (via Walrus), PactaForge ensures that not just transactions, but the full context of agreements — proofs, conditions, and outcomes — are persistent, auditable, and trustless.
PactaForge shifts smart contracts from simple transactions to complete, deterministic agreement systems.
On-chain multi-sig treasury governance for EVE Frontier alliances. In EVE, alliance leaders routinely disappear with the entire war chest — there is no trustless way to enforce spending rules or produce an audit trail.
Alliance Multi-Sig Treasury solves this with six Move modules on Sui:
- Treasury — Alliance vault where funds can only be released via approved proposals. No single person can withdraw.
- Roles — Member registry with combinable role bitmask (Commander / Treasurer / Elder / Auditor) and tiered signature thresholds: <100 SUI needs 2 sigs, 100-1000 needs 3, >1000 needs 4.
- Proposal — Complete multi-sig workflow: create, sign, execute, with 7-day expiry and on-chain audit events.
- Policy Agent — On-chain autonomous governance participant with 5 composable skills (auto-approve, rate-limit, trusted-list, balance-guard, cooldown). Not an AI wrapper — a deterministic,
auditable rule engine that acts as a co-signer 24/7.
- Gate Sync — Smart Gate extension enabling governance decisions to atomically update in-game gate access via PTB.
- Integration Examples — Read-only patterns showing how external protocols compose with treasury state.
Full-stack: 6 Move modules + Express backend with event indexer (KillMail, JumpEvent) + React tactical HUD frontend. 58 Move tests + 29 backend tests, all passing. Deployed on Sui testnet.
EF webCORE Website
EF webCore is a community-built intelligence and tooling platform for EVE Frontier — a unified hub of 11 live "cores" covering ship fitting, fleet intelligence, industry planning, base construction, tribe discovery, and developer infrastructure. Every core pulls from live game data across both the Stillness mainnet and Utopia sandbox environments, giving players and builders a single place to operate, plan, and build.
The platform serves three distinct audiences simultaneously:
players who need tactical and strategic tools without leaving the browser
developers who need reliable access to EVE Frontier's data layer,
the studio who benefit from a community that is more engaged, better informed, and actively extending the game's ecosystem.
EVE Frontier is a deep, complex game — and that complexity is a feature, not a bug. But complexity without tooling creates friction. Players struggle to answer basic questions: What hull fits my playstyle? Can I actually afford this module loadout? What structures do I need to reach fuel independence? Is the game even up right now?
On the developer side, the EVE Frontier data layer — the World API, Sui RPC, and GraphQL endpoints — is powerful but raw. Builders have had no centralized place to test queries, verify endpoint health, or understand the full item and structure graph before writing a single line of code.
EF webCore solves both problems at once.
How It Works — Technical Breakdown
Every core in the platform is connected to EVE Frontier's live data infrastructure. We consume the World API v2 for game state — ships, items, structures, tribes, and solar systems — and query Sui GraphQL and Sui RPC for on-chain data including chain checkpoints, transaction digests, and sequence numbers. Data is fetched in real time; there is no static cache masquerading as live information.
We support two environments in parallel:
Stillness — the live mainnet, where real player activity happens
Utopia — the sandbox/testnet, where developers build and test without affecting the live game
Switching between them is a single click across every core, meaning developers can prototype against testnet data and immediately verify behavior against mainnet.
Tribe identities, wallet addresses, and on-chain IDs are resolved directly from the Sui blockchain. Tribe Core surfaces each tribe's on-chain smart object ID, wallet address, and tax rate — data that lives on-chain, not in a centralized database we control. The Diagnostics Core monitors Sui RPC health in real time, tracking chain IDs and checkpoint progression so players immediately know whether an issue is game-side, chain-side, or local.
The Dev Core exposes a live GraphQL Explorer that lets builders write and execute queries against the Sui GraphQL endpoint directly in the browser — across both Utopia and Stillness — with no authentication setup required. This dramatically lowers the barrier to building on EVE Frontier's data layer.
The platform's data-rich cores — Ship Core, Industry Core, Structure Core, Chart Core — are built entirely on top of the EVE Frontier World API v2. We surface 390+ item types, 11 ship hulls with full stat layouts, 11 buildable structures with prerequisite chains, and 24,500+ solar systems across 2,279 constellations.
Ship Core connects to the pilot wallet lookup via the World API, letting players query another pilot's hangar by wallet address — a feature that has immediate applications for fleet scouting and market intelligence.
The Diagnostics Core monitors three critical services — World API, Sui RPC, and GraphQL — on a live auto-refresh cycle, returning HTTP status codes, response latency, and chain/checkpoint identifiers. When something goes wrong in the Frontier, players see it here before they see it on Discord. The troubleshooting protocol built into the core walks players through a structured diagnostic flow distinguishing game server issues from chain-level events from local connectivity problems.
Frontier Corm is an AI driven contract system intended to help provide players with breadcrumb tasks to get into larger and larger ships. In the future it will expand to function as conflict driver as groups of players interact with each other and the corms themselves become targets of player aggression. The ultimate goal of each corm network is to achievable continuity that does not require player intervention ( not possible with current game mechanics, maybe possible in the future? )
Shadow Broker Protocol is a trustless intelligence marketplace for EVE Frontier on Sui. Sellers upload encrypted audio intel, list it for sale on-chain, and buyers preview a short teaser before committing funds. The core problem is fair exchange: the seller should not have to reveal the intel before payment, and the buyer should not have to trust the seller blindly.
The project uses Walrus for storage, Seal for holder-gated decryption, and a Sui programmable transaction block for atomic purchase. The teaser is generated from the start of the real recording, so buyers get proof that the asset is genuine without getting the payload for free. Payment and transfer happen together, and only the wallet holding the IntelObject can recover the decryption key and play the full file.
The full flow has been verified in-game inside EVE Frontier Smart Storage Units: upload, list, preview, purchase, decrypt, and playback. That in-game SSU path is the supported environment for the project today. Browser wallet flow is not the reliable supported decrypt path because of a known Seal signing limitation with zkLogin-based wallets.
Self-executing diplomatic treaties for EVE Frontier. Sign on-chain, deposit collateral, break the pact, lose your stake.
Every war in EVE starts the same way: someone breaks a promise. Alliances negotiate pacts in Discord, but there's no enforcement. Betrayal costs nothing beyond subjective reputation.
Covenant makes betrayal expensive.
Two alliances sign a treaty on-chain, each staking SUI as collateral. An off-chain oracle monitors KillMail events — if a cross-alliance kill is detected, the contract automatically penalizes the violator with a graduated response:
- 1st violation: 20% of deposit forfeited — an incident, a warning
- 2nd violation: 40% forfeited — a pattern, escalation
- 3rd violation: 100% forfeited, treaty terminated — systematic aggression
This models how real diplomacy works. A single friendly-fire incident doesn't destroy a relationship. But repeated aggression escalates to full forfeiture. The game theory shifts: alliance leaders must actively police their own members.
The blockchain is the judge.
3-module system architecture:
covenant (core) — Treaty lifecycle: create, sign, graduated violation penalty, complete, cancel. The core state machine and escrow logic.
treaty_registry — Global treaty index with per-alliance reputation tracking. Records treaties signed, honored, violated, and computes compliance rate in basis points. Enables on-chain reputation queries.
gate_enforcer — Smart Gate extension that enforces diplomatic consequences in physical space. Violators' pilots get locked out of gates. Extends Covenant from on-chain record keeping to in-game world enforcement.
How it works:
1. Alliance A proposes treaty with SUI deposit
2. Alliance B co-signs with matching deposit — treaty activates
3. Off-chain indexer monitors KillmailCreatedEvent via Sui GraphQL
4. Cross-alliance kill detected — graduated penalty auto-applied
5. Treaty expires cleanly — both sides reclaim deposits
6. Gate Enforcer: violating alliance's members denied gate passage
Key features:
- Graduated penalty (20% / 40% / 100%) models real diplomatic escalation
- verify_violation() — anyone can independently audit, no trust in oracle required
- Treaty Registry with per-alliance compliance scores (on-chain reputation)
- Smart Gate enforcement — treaty violations have physical in-game consequences
- 24 unit tests, end-to-end verified on Sui Testnet
- Oracle decentralization roadmap: single — multi-oracle voting — fully permissionless
Built with Sui Move. 3 contract modules + TypeScript KillMail monitor.
Try it yourself:
Web: https://covenant-eve.vercel.app
Connect a Sui wallet (Testnet) to browse, propose, and sign treaties.
CLI: npx tsx demo/create.ts
Interactive treaty creation — one input + one confirmation = treaty on-chain.
Demo: npx tsx demo/demo.ts --dry-run
Watch the full lifecycle in 36 seconds — graduated penalty escalation to termination.
A community-funded charity system built on EVE Frontier smart storage. Veterans (Astartes) deposit Feral Data and Mummified Clones to earn Space Marine chapter tokens — then gift them to new players who can redeem them for Feral Data to jumpstart their journey.
Of the paths towards creating a toolkit for civilization, one of the factors that is most overlooked as against DAO governance mechanisms, logical turret efficiency systems, etc. is hope.
Hope that could be kindled by the sharing of support unburdened by tribal allegiance, and looking forward expansion by old and new players alike. A form of unhindered giving modality like the "Heralds of Big E" due to it's cultural relevance derived from the Warhammer 40K universe that many enthusiastic EVE Frontier players are fans of, will prove to be a great arm of the many toolkits for civilization.
