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.

The Core Loop
Chain events flow in → WatchTower fingerprints behavior and scores reputation
across six dimensions → scores publish on-chain as Sui Move objects → Smart
Assemblies read those scores in the same transaction they make access control
decisions → "deny docking if trust < 40" → player behavior adapts → new chain
events flow in → the cycle tightens.
Monolith runs in parallel. Same chain data, different question. Not "who is
this entity" but "is the economy intact." 40 detection rules across 20
checkers scan every event for supply discrepancies, bot patterns,
conservation-of-mass violations, spy indicators. When something breaks,
Monolith finds it before anyone notices.
Monolith's public API and webhook subscriptions give CCP a real-time economic
audit layer that doesn't exist today — bot detection, supply integrity, state
anomalies — consumable without building it themselves. WatchTower's on-chain
reputation oracle is equally available to CCP's own Smart Assemblies as it is
to any player-deployed gate.
No other entry in this hackathon closes this loop. Dashboards show you data.
Notification bots filter events. Aegis Stack creates a feedback cycle where
on-chain reputation changes on-chain behavior. 40 detection rules. Zero
competitors in this space.
---
Why This Had to Be Sui
EVE Frontier's entire player economy lives on Sui — kills, transfers, assembly
ownership, gate transits. That makes behavioral intelligence a blockchain
problem, not a game API problem.
The critical design choice: WatchTower's reputation oracle publishes scores as
Sui Move objects so Smart Assemblies can read them in the same execution
context they're making access control decisions. The trust check and the gate
check happen in the same transaction. No bridge. No off-chain lookup. No
oracle latency window where stale data lets a bad actor through.
Sui's object model makes this possible in a way EVM storage doesn't.
Reputation scores are owned objects with structured fields that Move code can
destructure and evaluate inline. A gate contract doesn't call an API — it
reads a Sui object that already exists in the transaction's object set. That's
sub-second trust verification at the protocol layer, not the application
layer.
We built four Move modules: watchtower::subscription (three paid tiers via
native SUI transfer, SubscriptionCap as owned objects, shared registry),
watchtower::reputation (6-dimension oracle scores queryable by any Smart
Assembly), watchtower::titles (earned title grants from behavioral
thresholds), and dossier::threat_registry (live-updating NFT intelligence
cards with oracle-pushed threat scores). 68+ transactions published including
53 reputation scores and 15 titles. Package:
0x3ca7e3af5bf5b072157d02534f5e4013cf11a12b79385c270d97de480e7b7dca
---
WatchTower — Behavioral Intelligence
WatchTower turns raw on-chain behavior into identity. Every entity that acts
on the frontier leaves a trace. WatchTower finds the patterns and builds
intelligence from them — who is this pilot, where do they operate, what have
they earned, what is their reputation worth. No manual tagging. No
self-reported data. The chain doesn't lie.
What it produces:
Entity Dossiers with stats, timelines, and danger ratings. Behavioral
Fingerprints covering temporal patterns, route analysis, social networks, and
OPSEC scoring. Earned Titles — deterministic names from chain stats: "The
Reaper" (50+ kills), "The Ghost" (30+ transits, zero combat), "The
Meatgrinder" (20+ nearby kills on a gate). A Story Feed that auto-generates
news from engagement clusters, streak milestones, and hunter activity. Kill
Networks mapping attacker-to-victim relationships with vendetta detection.
Danger Zones ranking systems by kill density with resolved system names.
Alt Detection through fingerprint comparison. AI Narratives powered by Claude
with template fallback. Corp Intel with combat rankings, member aggregation,
and rivalry detection.
Reputation System:
Every entity scored 0-100 across six dimensions — Combat Honor (clean kills vs
ganking), Target Diversity (range of opponents), Reciprocity (fair fights vs
one-sided), Consistency (stable behavior over time), Community (positive-sum
actions like gate building), Restraint (new player protection). These scores
publish on-chain and flow directly into Smart Assembly access control.
The Oracle: Standing watches on entities, gates, and systems with
Discord/webhook alerts. Movement detection, traffic spikes, killmail
proximity, hostile sighting. Set a watch from any entity's threat verdict card
and receive alerts when conditions trigger — in the web UI, via Discord
webhook, or both. NEXUS dispatcher pushes enriched events to third-party
builders. Discord bot with 15 slash commands. Three subscription tiers paid
in SUI on-chain (Scout ~$4.99/wk, Oracle ~$9.99/wk, Spymaster ~$19.99/wk).
Stripe as fallback rail.
Mission Control: A BYO-LLM intel agent wired to 10 WatchTower API tools.
Connect any OpenAI-compatible endpoint — Ollama, LM Studio, or hosted — and
query the intelligence database in natural language. "Who are the most
dangerous pilots right now?" "Is it safe to travel through system X?" The
agent calls tools autonomously, retrieves live chain data, and synthesizes
tactical briefings.
In-Game Embedded Intelligence: WatchTower renders inside EVE Frontier's Smart
Assembly browser panels. Approach a gate or kiosk and see the entity
intelligence card — trust score, reputation bars, danger rating, earned
titles, and a gate recommendation (ALLOW/DENY PASSAGE) — without leaving the
game. Cache-busted headers ensure the embedded view always shows live data.
Dossier NFTs:
On-chain NFT intelligence cards (DossierCard) that auto-update with live
threat and reputation data. Three tiers: INTEL (free), CLASSIFIED (0.5 SUI),
ORACLE (2 SUI). ThreatRegistry oracle pushes per-entity scores from Monolith's
40 detection rules. The card never goes stale — trade it, and you trade
access to that entity's live intelligence feed.
---
Monolith — Anomaly Detection Engine
40 detection rules across 20 checkers. Every rule is a pure function: (events,
states) -> anomaly or nothing. Pure chain-event architecture — zero
dependency on CCP's World API for dynamic data.
Five examples of what it catches: Economic rules (E1-E4) flag supply
discrepancies and duplicate mints — if items appear without a mint event or
vanish without a destruction event, Monolith sees it. Coordinated Buying
(CB1-CB2) detects fleet staging signals from clustered wallet activity. Bot
Pattern (BP1) identifies automated transaction cadences. Tribe Hopping (TH1)
flags rapid corp changes as a spy indicator. OwnerCap Transfer (OC1) detects
ownership delegation and capability handoffs as behavioral signals.
...and 15 more checker categories covering object versioning, killmail
integrity, dead assemblies, engagement reconstruction, velocity anomalies,
wallet concentration, config changes, sequence gaps, continuity violations,
inventory auditing, POD verification, market manipulation, orbital zones,
feral AI, and chain state verification via Sui GraphQL.
Canvas2D heatmap renders 24,502 solar systems at 60fps. Item ledger tracks
every mint, transfer, and destruction. Public API v1 for anomaly queries.
Webhook subscriptions for push. Discord alerts by severity. Auto-filed GitHub
issues on CRITICAL. In-game embedded threat feed shows live anomalies inside
Smart Assembly browser panels with auto-polling and system-level filtering.
---
Architecture
Both systems ingest from Sui RPC + GraphQL on the Stillness testnet —
killmails, gate events, entity activity, object state. All data is live
chain data, not cached or simulated.
WatchTower: Indexer → Scoring Engine (fingerprinting, reputation, titles, AI
narratives) → SQLite WAL → 54 tier-gated REST endpoints + SSE live feed +
Discord bot → React 19 frontend on Vercel.
Monolith: Indexer → Detection Engine (40 rules, item ledger, chain state
verification) → SQLite WAL + FTS5 → 38 REST endpoints + Public v1 + webhooks +
Discord alerts → React 19 frontend with Canvas2D map on Vercel.
Reputation scores flow from WatchTower's scoring engine → on-chain via Sui
Move → readable by any Smart Assembly in the same transaction context.
---
By the Numbers
1,628 tests across both systems. 14,524 entities fingerprinted. 796+ anomalies
detected. 24,502 systems mapped. 67,880+ chain events ingested. 525+
killmails analyzed. 299,489 state transitions tracked. 40 detection rules
across 20 checkers. 92 API endpoints. 4 Sui Move modules. 15 Discord
commands. 68+ on-chain transactions. Both systems live in production on
Stillness.
---
Live Demo
WatchTower: https://watchtower-evefrontier.vercel.app/
WatchTower In-Game Embed: https://watchtower-evefrontier.vercel.app/embed
Mission Control: https://watchtower-evefrontier.vercel.app/mission-control
Monolith: https://monolith-evefrontier.vercel.app/
Monolith In-Game Embed: https://monolith-evefrontier.vercel.app/embed
Website: https://thewatchtower.xyz
Demo Video: https://youtu.be/I9_B6krfbXc
Repo: https://github.com/AreteDriver/watchtower
---
Track: Utility
Built by: AreteDriver

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.

Wreckage Insurance Protocol
On-Chain Combat Insurance & Salvage Protocol for EVE Frontier
"High risk, high reward." — The definitive safety net for deep-space explorers.
## 🎯 The Problem
In EVE Frontier, losing a vessel means months of progress instantly wiped out. This severe penalty stifles combat readiness and economic velocity. Furthermore, battlefield wreckage lacks a liquid, ownership-driven marketplace for disposal and recycling.
## 💡 The Solution
Wreckage Protocol acts as a decentralised "Lloyd's of London." Powered by Sui, we merge combat hedging with salvage recycling into a robust Web3 circular economy:
- 🛡️ Automated Claims: Triggered by real-time on-chain Killmails via World Contracts. Once a ship is destroyed, the protocol instantly handles deductibles and pays out SUI compensation.
- ♻️ NFT Salvage Rights: Combat losses automatically mint a "Salvage NFT." Industrial guilds and scavengers bid on these rights in a global auction, turning space debris into fresh materials.
- 💰 DeFi Risk Pools: Non-combatants can supply liquidity to payout pools, earning premium yields funded by pilots cosmos-wide.
## ⚡ Why Sui?
- Object-Oriented Primitives: Policies and Salvage NFTs are native Sui Objects, rendering them inherently transferable and liquid.
- High-Concurrency Auctions: Each salvage auction operates as a standalone Shared Object. Bidding remains flawlessly smooth, even amidst thousand-player fleet battles.
- Oracle-Free Verification: By directly reading in-game on-chain Killmails, we securely eradicate fraudulent "scuttling" claims without external dependencies.

Frontier Trade Routes is a privacy-aware logistics and intel market built for the EVE Frontier x Sui ecosystem.
Instead of exposing exact live coordinates, the app shows region-level demand and route pressure so players can discover profitable trade activity without turning the interface into a targeting tool. Buyers can publish delivery contracts with budget, minimum reputation, and minimum stake requirements. Carriers accept orders by locking stake, and route information is revealed in stages: pickup first, destination later.
The system combines fuzzy heatmaps, gated order matching, staged reveal, reputation tiers, staking, intel validation, and mutual insurance into a single workflow. This helps players coordinate hauling, evaluate route risk, reward reliable carriers, and protect buyers when runs fail.
In short, Frontier Trade Routes creates a trust layer for player-driven logistics: discover demand, accept work, verify intel, lock stake, protect high-risk routes, and settle outcomes on Sui.

Military-grade, post-quantum hardware firewalls protecting autonomous EVE Corporate Treasuries from zero-day logic hacks in sub-25ms.

Dead Simple Storage Manager
Tribal shared storage for EVE Frontier - set up in under 30 seconds.
Sharing resources with your tribe should be easy. Right now, EVE Frontier storage units are personal - there's no native way for tribe members to deposit and withdraw from a common stockpile. Dead Simple Storage Manager fixes that.
What it does
Adds a shared tribal inventory into any Smart Storage Unit. Tribe members can deposit items from their hangar into a communal pool, and any other member of the same tribe can withdraw them.
This is multi-tenant: many tribes can have their own unique tribal storages within the same storage units, each inaccessible to members of other tribes.
How it works
The manager authorizes the Warehouse Receipts extension (enabling verifiable deposit tracking) and freezes the configuration so it can't be tampered with. Permissions to access a tribal storage are handled automatically by a character's tribe membership.
Once initialized, Dead Simple Storage Manager exposes three sections:
- Hangar - personal items belonging to the storage unit owner or other player accessing the storage
- Personal warehouse - your own Warehouse Receipts-backed storage
- Tribal storage - a shared inventory visible and accessible to all tribe members containing warehouse receipts within a Tribal Vault
Moving items between storages is drag-and-drop. Withdrawing is instant.
Why it matters
Shared logistics is the backbone of coordinated play. Whether your tribe is pooling fuel after a rift harvest, staging supplies for a forward deployment, or just running a communal workshop, Dead Simple Storage Manager removes the friction of manual jet-can transfers and trust-based handoffs - and it takes less time to set up than it does to read this description.

EveMBA seamlessly integrates MBA education with EVE Frontier gameplay, offering an immersive copilot/mentor learning experience in the realm of interstellar strategy and business.

This is a Storage Unit based sweepstakes system. Players can create sweepstakes by defining the prize, prize quantity, total tickets, and ticket price, while other players use EVE tokens to buy tickets and join the draw. Once tickets are sold, all proceeds go to the creator; before sellout, the creator can cancel the sweepstakes at any time and all paid EVE is refunded automatically. Winner selection uses the official Sui RandomGenerator flow to improve fairness and verifiability.
Ease of Use
No detailed parameter inputting required, mostly auto-configured just Ctrl C + Ctrl V your SU address!
Connect your wallet in-game with One single click.
Use Item names as input! No remembering type ID.
A Sweepstakes game is Auto-drawn when all the tickets are sold!
Built-in Chinese Interface, just click a button and switch the language!
Uses Sui RandomGenerator to ensure Nothing is Rigged.
Averaged chances across each tickets.
The more ticket you buy, the bigger the winning chance is! It will also cost you more!
Set the Name of the game whatever you want!
Set the Number of tickets however you want!
Set the Price of each ticket however you want!
Regret making a game? No worries! Cancel & Refund has you covered! (Only for Game Creator)
Links

Small LLM based companion with access to game api and sui interface to enhance player experience and immersion.