For judges
Five minutes. All live. Nothing mocked.
Everything below runs on NEAR testnet with real transactions. Where a run simulates something (a studio going silent, scripted test players), it says so.
Watch the demo first →- 1
Play
Enter a name, gather, forge a Lantern. Your browser makes a key and signs every move; every rule runs in the one wasm core the studio seals.
Enter Embergate → - 2
Check the vault
Press Check. Your browser fetches your proof and verifies it against the root it reads from NEAR itself. (If you joined after the last seal, it says so: the studio re-seals every six hours.)
Is my stuff in there? → - 3
Kill a studio
This studio sealed its world, got it verified green, then stopped its heartbeat. Press Release it: a real NEAR transaction the contract alone allows.
Release a silent studio → - 4
Bring it back
The page rebuilds the game from NEAR and FastFS alone: the release's signature, the package's hash, the decryption, the core, every player's items, a boot with zero imports.
Watch the eight checks → - 5
Play on
Press Play on. The same game, run by your browser on the core that came out of the escrow. Try the C++ football club or the C city too.
Revive the C++ game → - 6
Try to break it
Six real attacks on live, locked escrows: early release, fake heartbeat, fake seal, tampered build, replayed quote, double release. Each refused on chain.
Cheat the escrow →
Every claim, and where it is proven
Check it without our site
Any escrow’s state and its keys, straight from NEAR:
curl -s https://test.rpc.fastnear.com -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"query","params":{
"request_type":"call_function","finality":"final",
"account_id":"encroe-embergate.testnet",
"method_name":"status","args_base64":"e30="}}'
# from the repository
make test # Rust: CKD vectors, IBE, verifier, the escrow, the factory
cd web && npm ci && npm test # the browser code against real released dataOr ask your own AI
The site is also an MCP server: list escrows, inspect one, release a silent studio’s game, bring a released game back with every check.
claude mcp add --transport http encroe https://encroe.vercel.app/api/mcpThe preservation agent’s log
Where to look in the code
- The escrow contractcontracts/encroe-escrow/src/lib.rs
- The factory and directorycontracts/encroe-factory/src/lib.rs
- The verifier the enclave runscrates/encore-verifier/src/lib.rs
- Sealing: CKD identity, IBE, the package, player leavescrates/encore-crypto/src
- Game cores in Rust, C++, C, Zig and Go, and their interfacecores/README.md
- Bringing a game back, in the browserweb/lib/encroe/revive.ts
- Sealing in the browserweb/lib/encroe/seal.ts
- The item handover on NEAR, and its token on Basecontracts/encroe-items/src/lib.rs
- The preservation agent and the MCP serverweb/lib/encroe/agent.ts
- The studio's botscripts/studio/bot.sh
What we disclose
- Testnet only. No mainnet transaction was sent.
- In every recorded release, we stopped the studio’s heartbeat ourselves: the only way to show a studio disappearing on demand. The contract cannot tell the difference, which is the point.
- The sealed worlds hold players we played by hand and players scripted through the same signed moves.
- The enclave is OutLayer’s; its operators are not trusted: a run counts only after NEAR’s own DCAP verifier accepts its quote.
- A world holds 64 players. A revived world runs in each player’s browser; shared hosting, paid on proof, is designed, not built.
- Item claims were relayed to Base Sepolia from a testnet account of the author’s other project (Klear’s); anyone can relay one, since the token checks the MPC signature, not the sender.