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.
Singu Hunt is an on-chain hunt game in EVE Frontier where players race through real gates and SSUs, collect Singu Shards, return to base, and earn permanent achievements. It links real in-game movement to blockchain state with secure Sui Move verification, anti-cheat logic, and 3-layer protection against frontend injection. Singu Vault turns those achievements into long-term rewards, letting players redeem NFTs for rewards or use them in a principal-oriented staking flow. Together, they connect gameplay, ownership, and community participation in one ecosystem.
Official: https://eveuluv.me/
Trailer&Intro(Youtube): https://youtu.be/DWrJCcNGC0c
GitHub(4 repos): https://github.com/EveULuvMe/singuhunt-contracts, https://github.com/EveULuvMe/singuhunt-app, https://github.com/EveULuvMe/singuvault-contracts, https://github.com/EveULuvMe/singuvault-app
YouTube: https://youtu.be/DWrJCcNGC0c
Dapps: now land on EVE Frontier Utopia, will land on Stillness soon.
Landing Page: https://eveuluv.me
3 lines of Game Highlights
Fun: Singu Hunt turns EVE Frontier travel, routing, timing, and risk into a fast competitive treasure hunt with real first-to-arrive tension.
Community impact: It creates repeatable daily events that bring players together, reward participation, and can support a more self-sustaining community economy through Singu Vault.
What makes it different: Unlike ordinary web3 games, Singu Hunt binds gameplay to real EVE Frontier world objects and verifies in-world interaction on-chain with anti-cheat protections.
[Details] Singu Hunt Introduction
### 1. Solo Race
Players register, rush to the active mini gates, collect all required Singu Shards, and return them to the home gate before anyone else. The fastest registered players compete for a limited winner pool, and successful completion mints a permanent achievement NFT.
Contract summary: Uses open_registration, start_hunt_with_selection, collect_singu_shard, deliver_singu_shard, and claim_achievement; winner slots are calculated on-chain from registered player count.
Difficulty: Medium. It is easy to understand, but highly competitive because every shard is first-come, first-served.
On-chain object ids and package id:
Package ID: 0x0fffba7ceaf4c46a27195f484a32f478a5b3dccff4c1628a614c1224b52ee467
Home / Start / End Gate: 0xf27500312bd59533d7f99fd575efb0b798d81437066ae79212d880501cadacdd
Mini Gate 1: 0x4e3eb175c4bac0edf3509b8681bf97d6439fc17bd462422f305f3db07599c36c
Mini Gate 2: 0xe9799223e7a160bb25c41cbd581631ca330ed1e81ef5e799bad962e646f48d45
### 2. Team Race
Players register individually, then the contract finalizes randomized 3-player teams before the hunt begins. Each team must collectively complete all required checkpoints and return to base, with every member of a winning team receiving an achievement NFT.
Contract summary: Uses finalize_team_registration, TeamAssignmentKey, TeamRosterKey, TeamGateClaimKey, collect_singu_shard, and claim_team_achievement; progress is tracked per team instead of per individual.
Difficulty: High. Coordination, timing, and team reliability matter more than raw speed.
On-chain object ids and package id:
Package ID: 0x0fffba7ceaf4c46a27195f484a32f478a5b3dccff4c1628a614c1224b52ee467
Home / End Gate: 0xf27500312bd59533d7f99fd575efb0b798d81437066ae79212d880501cadacdd
Mini Gate 1: 0x4e3eb175c4bac0edf3509b8681bf97d6439fc17bd462422f305f3db07599c36c
Mini Gate 2: 0xe9799223e7a160bb25c41cbd581631ca330ed1e81ef5e799bad962e646f48d45
### 3. Deep Decrypt
Deep Decrypt is a puzzle-focused mode where players solve a daily decrypt or lore challenge instead of physically collecting all shard checkpoints. It is designed to reward knowledge, interpretation, and fast reasoning inside the Singu universe.
Contract summary: Uses claim_decrypt_achievement with signed short-lived solve tickets; the contract enforce registration, expiry, replay protection, and limited winner slots for the mode.
Difficulty: Medium to High. Mechanical execution is lighter, but puzzle-solving speed becomes the deciding factor.
On-chain object ids and package id:
Package ID: 0x0fffba7ceaf4c46a27195f484a32f478a5b3dccff4c1628a614c1224b52ee467
Home Gate: 0xf27500312bd59533d7f99fd575efb0b798d81437066ae79212d880501cadacdd
SSU 1: 0x0703e74e68bea379250206b285904035649dfa2c3a544fb4571967f264a9877e
SSU 2: 0xf956e5ca8447056f5bad7044cd60c8c78609ca703a2d4c797bc0e944e5206156
SSU 3: 0x1d238ac1faca0d5f6e6efd132f1a3b1dc5e172d68e2547d7da10c85798d247a3
### 4. Large Arena
Large Arena expands the hunt into a bigger and more dangerous traversal space, intended for heavier infrastructure and a broader combat environment. It is the mode best suited for spectacle, area control pressure, and larger map movement.
Contract summary: Uses the same shared hunt and winner framework as the main package, but is mapped to heavy-gate hardware and longer session timing in the scheduler.
Difficulty: High. Travel distance, exposure, and broader field pressure make execution harder than the base race mode.
On-chain object ids and package id:
Package ID: 0x0fffba7ceaf4c46a27195f484a32f478a5b3dccff4c1628a614c1224b52ee467
Home Gate: 0xf27500312bd59533d7f99fd575efb0b798d81437066ae79212d880501cadacdd
Heavy Gate 1: 0x39913c81d0fec7f35cbcd93b5672e24a7a4a737f474c493b5c8f91c4beacc81e
Heavy Gate 2: 0xffacc0a31c2043738cacd150a7ffbbabf258c2a45aa49df09b1b2d1376eec364
Heavy Gate 3: 0x1840453d141280f202802c3eb2a525affe572a887125f47e1dbf43dee5786b31
### 5. Obstacle Run
Obstacle Run forces players to clear checkpoints in strict sequence rather than in any order. It adds route discipline and pressure, and in the current design it is also the mode where turret behavior becomes actively hostile to participants.
Contract summary: Uses collect_singu_shard with on-chain sequential enforcement via E_INVALID_GATE_ORDER; a player can only claim checkpoint n after completing checkpoint n-1.
Difficulty: Very High. It removes route flexibility and punishes mistakes immediately.
On-chain object ids and package id:
Package ID: 0x0fffba7ceaf4c46a27195f484a32f478a5b3dccff4c1628a614c1224b52ee467
Home / End Gate: 0xf27500312bd59533d7f99fd575efb0b798d81437066ae79212d880501cadacdd
Mini Gate 1: 0x4e3eb175c4bac0edf3509b8681bf97d6439fc17bd462422f305f3db07599c36c
Mini Gate 2: 0xe9799223e7a160bb25c41cbd581631ca330ed1e81ef5e799bad962e646f48d45
SIngu Vault's Package ID:
Use StableLayer's package (0x9c248c80c3a757167780f17e0c00a4d293280be7276f1b81a153f6e47d2567c9)
The Eternal Chronicle is a decentralized narrative engine that transforms on-chain events from the EVE Frontier blockchain universe into permanent, AI-generated chronicle entries. It monitors the Sui blockchain for milestone events — gate deployments, combat kills, pioneer arrivals, ownership transfers, and more — then runs a six-stage pipeline:
Detect milestone events via the eve-eyes indexer API
Generate narrative prose in an epic, archaic-formal voice using Gemini 2.5 Flash
Generate concept artwork in a dark space-opera aesthetic using Gemini image generation
Upload artwork to Walrus decentralized blob storage
Build individual chronicle HTML pages from templates
Publish a static site to Walrus Sites with a hero carousel and chronological feed
Each chronicle entry is idempotent (tracked by transaction digest), cost-tracked, and permanently stored on decentralized infrastructure. The system supports three modes: continuous watch polling, single-event processing, and local demo generation.
Tech stack: Node.js (ES Modules), Gemini AI (via OpenAI-compatible SDK), Walrus blob storage & Sites, Vitest + Playwright for testing.
Collective intelligence for EVE Frontier. A prediction market where on-chain game events are the oracle.
Traditional prediction markets need external oracles — someone trusted to say "this happened." EVE Frontier doesn't have this problem. Every kill, every gate jump, every item destroyed is already an immutable on-chain event. The chain data IS the oracle. No Chainlink, no dispute resolution, no trust required.
Players stake SUI on predictions about real in-game outcomes. Settlement is determined entirely by on-chain event counts that anyone can independently verify.
How it works:
1. Creator publishes a market ("Will System X see >20 kills this week?")
2. Players stake SUI on YES or NO — odds shift with each bet
3. Off-chain indexer counts matching EVE events via Sui GraphQL
4. Contract auto-settles based on observed count vs threshold
5. Winners claim proportional payout (minus 2% protocol fee)
module system architecture:
- augury (core) — Market creation, betting, resolution, payout. 457 lines.
- resolver_registry — Multi-oracle M-of-N quorum resolution (v2 decentralization). Multiple resolvers submit counts independently; market resolves when quorum agrees. 263 lines.
- gate_oracle — Smart Gate extension powered by market odds. Gates deny passage when prediction markets show high danger probability. First concrete example of prediction market composability. 176 lines.
Key features:
- 3 EVE event types: KillMail, JumpEvent, ItemDestroyed
- Multi-oracle decentralization (v2 implemented, not just roadmapped)
- Smart Gate composability (market odds -> gate access control)
- End-to-end verified: indexer counted 63 JumpEvents and auto-resolved a market on testnet
- 29 unit tests (augury) + 94 (gate_oracle) + 275 (resolver_registry) = 398 test lines
EVE Frontier PvE Ship Insurance is a decentralized insurance protocol built with Move on Sui that protects player ships only against environment-driven (PvE) risks in EVE Frontier.
The protocol is designed for the EVE Frontier × Sui Hackathon 2026 – “Toolkit for Civilization”, providing an on-chain risk management layer for in-game assets. All policy terms, claims, and payouts are transparent and enforced by smart contracts.
In EVE Frontier, ships are valuable and can be lost permanently due to:
Asteroid collisions
Black hole / gravitational anomalies
Rogue / feral AI drone swarms
Other game-defined environment events
Currently, there is no native, trustless insurance system to protect players from these losses.
Goal: Build a fully on-chain insurance protocol that:
Covers only PvE environmental hazards
Automatically verifies losses using game data and oracles
Pays out trustlessly when conditions are met
Allows the community to underwrite risk and earn yield
PvE-only coverage
Explicitly insures losses caused by environment hazards, strictly excluding PvP and fraudulent/self-inflicted losses.
Automated on-chain claims
Uses Kill Mail data and an Environmental Oracle. Claims are evaluated by deterministic smart contract logic.
Instant payouts
Once a claim is approved, payout is calculated and sent automatically. No manual adjusters or human intervention.
Community underwriting pool
Players can deposit capital to the Insurance Fund and earn a share of premiums proportional to staked capital.
Dynamic risk-based pricing
Premiums depend on:
Ship type
Region risk profile
Historical loss data (via adjustable risk parameters)
P/S:
20% me.
80% AI tools.
Coding isn’t my profession — but the passion is real.
I just want to turn the ideas in my head into something real.
Still learning. Still building.
X: OlympusXVN
Defensive telemetry for EVE Frontier turret operators.
Sentinel is an EVE Frontier dashboard for monitoring turret assemblies and tracking their interactions with other players or NPCs.
The Sentinel dashboard gives you visibility into who or what is scouting or attacking your assets throughout the EVE galaxy.
Displaying Turret Smart Assembly objects owned by the logged in wallet
Event history and threat intelligence from indexed on-chain turret events
Solar-system mapping for working around the location obfuscation in EVE, players can assign solar-systems to their network nodes
Galaxy plotting by network-node; assign solar systems to network-nodes to map turrets
Live operator view
NOTE: This app required PriorityTargetUpdateEvent s which are not yet published on-chain. To emulate them, the app has mock data loaded at https://ef-sentinel.xyz/demo
NOTE 2: This app reads and uses Stillness, but it is not a move contract so it does not have a special package ID.
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.
The Frontier is meant to be player-built. But right now, most players can't write a single line of Move. First Move changes that.
First Move is a free, interactive course that teaches the Move programming language from scratch, designed specifically for EVE Frontier players who want to go from zero coding experience to deploying their own smart contracts in-game.
🔗 Try it now → evefrontier.space/move
EVE Frontier's mod ecosystem depends on smart contracts written in Move on Sui. The problem? There's a steep learning curve, scattered documentation, and nothing purpose-built for Frontier players. First Move solves this by providing a structured, beginner-friendly learning path that takes players from basic syntax all the way to writing and deploying real smart contracts, no local toolchain setup required.
This isn't a proof of concept. It's live, functional, and ready for players to use today.
First Move is designed as a complete learning system, not a one-off tutorial:
Progressive curriculum - Modules build on each other, introducing concepts incrementally so players aren't overwhelmed
Interactive code editor - Write, run, and test Move code directly in the browser with instant feedback
Frontier-contextualised examples - Lessons use EVE Frontier scenarios and concepts, so you're learning the language through the game itself
Self-paced structure - Players can pick up where they left off and progress at their own speed
The course is architected to scale, new modules and lessons can be added as the Frontier ecosystem evolves.
The course is fully built and operational at evefrontier.space/move. Players can:
Browse the full course structure and curriculum
Work through interactive lessons with embedded code editors
Write and execute real Move code in the browser
Progress from fundamentals to smart contract deployment
No installs. No configuration. Open the link and start learning.
This mod doesn't just add a feature to the Frontier - it multiplies the number of people who can build for it. Every player who completes First Move becomes a potential mod creator. That means:
More mods being built
More diverse ideas entering the ecosystem
A stronger, more self-sustaining player-driven economy
The bottleneck for EVE Frontier's growth isn't ideas - it's builders. First Move removes that bottleneck.
EVE Frontier's identity is built on the promise that players shape the world. First Move leans into that philosophy by giving players the actual skills to do it. The course doesn't teach generic Move — it teaches Move through the lens of the Frontier, using in-game concepts and scenarios throughout.
This feels like infrastructure the Frontier was always going to need. We just built it first.
Most hackathon entries add something to the game. First Move teaches players how to add things themselves. It's a meta-mod, a mod that generates more mods. We haven't seen another entry tackling the education and onboarding gap, and we believe lowering the barrier to entry is one of the highest-leverage things you can build for a player-driven ecosystem.
The course is designed for players and new developers:
Clean, intuitive interface - no clutter, no jargon upfront
In-browser code editing - zero setup friction
Progressive difficulty - you're never thrown into the deep end
Frontier-themed throughout - it feels like part of the EVE Frontier world, not a generic coding bootcamp
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.
