Rust
Embergate
a crafting world: six nodes, forged relics, the Phoenix
- built
- rustc → wasm32
- core
- 49ff0c57f10f24b9…
- escrow
- encroe-kill-827e.testnet
- on NEAR now
- reading…
Encroe · a game escrow on NEAR
A studio seals its game server into a NEAR contract that has no keys. While the studio lives, anyone can check the sealed build is real. If it goes silent, anyone can release it, and the game goes to its players with everything they earned.
The problem
2024
The Crew's servers went dark, and the game people paid for went with them.
Jan 2026
Anthem's servers shut for good, and everything its players earned with them.
1.29M
Europeans signed the Stop Killing Games initiative.
Declined
The EU declined to legislate. An end-of-life promise cannot be enforced: when it matters, the studio is gone.
The answer
The studio seals its server core and every player's items, encrypted to a key that exists only inside NEAR's MPC network. Not the studio's, not ours.
NEAR MPC · key derivation
An Intel TDX enclave decrypts the sealed build, runs it, and checks it serves every sampled player exactly. NEAR's own DCAP verifier checks the enclave before the contract believes it. A broken build turns the badge red.
TDX · NEAR DCAP verifier
Each player proves their items are inside, against the root NEAR holds, without revealing anyone else's. Their browser does the checking.
salted Merkle root
The studio keeps signing in. If it goes silent past its grace period, anyone (a player, a fan, an agent) can release the escrow. The contract has no keys: nobody can stop it or move it early.
a keyless contract
NEAR's MPC network publishes the key. Anyone takes the package from NEAR, checks every hash against what the enclave verified, and runs the server, with everyone's items intact.
FastFS · your browser
No lawyer, no escrow agent, no permission, no key anyone holds.
Try it yourself
Five games in five languages: Embergate (Rust), Matchday (C++), Neon City (C), Starhaul in 3D (Zig) and Orchard (Go). Every move is signed by a key your browser makes, and every rule runs in the one server core the studio seals.
Pick a game →Once the studio seals an epoch, ask whether your items are inside. Your browser reads the root from NEAR and checks your proof itself.
Is my stuff in there? →A studio here has gone silent. Release its escrow: one click, a real NEAR transaction, nobody's permission. The contract checks the silence, not us.
See a killed studio →Watch your browser rebuild the game from NEAR alone: eight checks, from the key's signature to every player's items. Then play on, with no server at all.
Bring a game back →A released world's items can leave the game: NEAR Chain Signatures signs your claim with a key nobody holds, and a token on Base Sepolia mints exactly what you earned, once.
Claim after a release →Don’t trust this page
Each row is the escrow’s own status() and its access keys, read from NEAR testnet as this page loaded. Each run, every transaction, is written up in the repository.
Reading NEAR testnet…
Any engine, any language
A game server compiled to WebAssembly is just bytes: the enclave runs them, the verifier judges how they behave, and a browser brings them back. Five games in five languages, each sealed into its own keyless escrow and checked by the same pinned verifier; three of them released and revived, two holding live worlds.
Rust
a crafting world: six nodes, forged relics, the Phoenix
C++
a football card club, the Ultimate Team genre: packs, rated cards, matches, a transfer market
C
an open-world city economy, the GTA Online genre: jobs, vehicles, heists, property
Zig
a space freight economy: mine asteroid belts, refine alloy, fly contracts, buy ships
Go
a farm and county fair: tend rows and hives, press cider, make jam, win ribbons
How NEAR makes this possible
Every piece of the promise is a NEAR primitive. Take one away and the escrow needs someone to trust again. The same network that releases a game signs its players’ items onto another chain.
The key
v1.signer-prod.testnet
Derives a key for each escrow's own identity (confidential key derivation, domain 2) and publishes it only when that contract asks. Before the release, nobody holds it: not the studio, not us.
The handover
encroe-items · domain 0
The same MPC network signs for a keyless contract on other chains. After a release, it signs each player's claim to their own sealed items, once, and a token contract on Base Sepolia mints exactly that.
The proof
tee-verifier-2026-07-22.testnet
Checks Intel TDX quotes on chain. The escrow accepts an enclave's verdict only after this contract verifies its quote, bound to that exact run.
The rules
0 access keys
An account with no keys can never change its code. The factory creates every escrow without one, so the release condition it is born with is the one it dies with.
The studio
the studio's wallet
A studio creates its escrow, seals its world, heartbeats and ends service from its own wallet, in the browser. Its package key leaves the tab only encrypted to the enclave's keystore.
The enclave
outlayer.testnet
Runs the pinned verifier inside Intel TDX, with the studio's sealed key row readable only by that build, for that escrow. Its operators are not trusted: NEAR checks the hardware.
The package
test.fastfs.io
The sealed game lives on NEAR itself, as transaction data. Bringing a game back needs no studio server: the hash NEAR holds decides what is real.
The wait
yield · resume
One release transaction asks the MPC network and hears back; one verify asks OutLayer and hears back. The contract keeps the answer, so the state on chain is the story.
Beyond one game
Create your game's escrow from your wallet: keyless from birth, one transaction.
Every escrow, read live from NEAR: whose game, verified or not, how long the heartbeat holds.
Releases silent studios' games and brings them back, on its own. Also an MCP server for your AI.
What happens next
Working on testnet
The revived core runs in each player's browser, from NEAR and FastFS alone, with every player's items.
Bring a game backNEAR Chain Signatures signs a player's claim to their own sealed items; a token on Base Sepolia mints exactly that, once.
Claim after a releaseEvery 30 minutes, the preservation agent releases silent studios' games and brings every released game back, with all its checks.
The agent's logThe site is an MCP server: list escrows, inspect one, release a silent studio's game, bring it back, find a player's items.
Connect an agentDesigned, not built yet
One shared world after a release: community hosts run the released core in an enclave, and a pool pays them only for the windows NEAR's DCAP verifier confirms they served it.
The handover runs on Base Sepolia. The same MPC key signs for Ethereum; an Ed25519 domain would reach Solana.
Rust, C++, C, Zig and Go are sealed today. C#'s WebAssembly runtime needs host imports the pinned verifier refuses, so it needs a new verifier first.
A world holds 64 players today. Paged snapshots under one root lift that; the escrow, verifier and checks stay as they are.
Rust
a crafting world: six nodes, forged relics, the Phoenix
C++
a football card club, the Ultimate Team genre: packs, rated cards, matches, a transfer market
C
an open-world city economy, the GTA Online genre: jobs, vehicles, heists, property
Zig
a space freight economy: mine asteroid belts, refine alloy, fly contracts, buy ships
Go
a farm and county fair: tend rows and hives, press cider, make jam, win ribbons
0 access keys · epoch 20
This site's public world: the studio's bot seals it, the enclave verifies it, players check their items
0 access keys · epoch 1
Released, then its items handed over: a player's sealed items minted on Base Sepolia through Chain Signatures
0 access keys · epoch 2
Neon City's world, sealed by the browser's own code and verified green
0 access keys · epoch 17
Starhaul, a 3D space game whose server is Zig: its world sealed and verified green
0 access keys · epoch 1
Orchard, a farm game whose server is Go: its world sealed and verified green
0 access keys · epoch 1
Embergate's played world: sealed, verified green, checked by its own players
0 access keys · epoch 1
Killed from this site: a visitor's click released it, the browser brought it back
0 access keys · epoch 1
A silent studio: released by a stranger, revived and played on in a browser
0 access keys · epoch 2
The first full life: a broken build caught red, the real one green, the studio's silence, the release