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. 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. 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. 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. 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. 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. 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

The key exists only in NEAR's MPC network until the escrow asks for itGO_NO_GO §E1; every release check →Only the pinned verifier, run for this escrow, can read the studio's sealed keyGO_NO_GO §E2: a thief build and a direct call refused →A broken build turns the badge red; the real one green only after NEAR's DCAP verifierlife-52e4, steps 3 to 7 →A replayed TDX quote is refusedlife-52e4 step 8, and attack 05 on /break, live →Nobody releases while the studio liveskill-827e step 8, and attack 01 on /break, live →A stranger releases a silent studio; the game comes back in a browser; play goes onkill-827e →A visitor does it from the site, with no walletkill-beaa →Rust, C++ and C game servers all pass the same pinned verifier and come back in a browserthe cores run →Zig and Go too: two more games sealed into factory escrows and verified green; each rebuilds byte for bytethe engines run →A studio seals from its browser alone, and the enclave and NEAR accept itbrowser-seal →An AI agent nobody wrote for Encroe preserves a game: Claude Code, with only the MCP server, released a silent studio's game and brought it back, all 8 checks, in 48 sthe agent run →A released world's items leave the game: minted on Base Sepolia through NEAR Chain Signatures, signed by a key nobody holds; forged, inflated and repeated claims refusedthe items run →The site's public world is sealed and verified; players check their own items from the browserencroe-embergate, ember-3924 →The browser's crypto matches the Rust tools byte for byterelease.test.ts, proof.test.ts: real released epochs and on-chain roots →

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 data

Or 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/mcp
The preservation agent’s log

Where to look in the code

What we disclose

JUDGES.md, with every transaction