Proof
Don’t take our word. Take NEAR’s.
Every claim Encroe makes was run on NEAR testnet and written up with its transactions. Where a run simulated something (a studio going silent, scripted players), its write-up says so.
Try to break it →
Six real attacks on live, locked escrows. Each refused on chain, in the contract's own words.
The judges' path →
Five minutes: play, check the vault, kill a studio, bring it back, play on.
The agent's record →
Every game it brought back, with all eight checks, every 30 minutes.
An AI agent did it →
Claude Code, unmodified, with only our MCP server: it released a silent studio's game and brought it back, all 8 checks, in 48 s.
Items on another chain →
A released world's items minted on Base Sepolia through NEAR Chain Signatures; forged, inflated and repeated claims refused.
Every attack, and its cost →
Each way to cheat Encroe we tried, what stopped it, and where the refusal is recorded.
Every run, on chain
- encroe-embergate.testnet
This site's public world: the studio's bot seals it, the enclave verifies it, players check their items
- handover.encroe.testnet
Released, then its items handed over: a player's sealed items minted on Base Sepolia through Chain Signatures
- neon-city.encroe.testnet
Neon City's world, sealed by the browser's own code and verified green
- starhaul.encroe.testnet
Starhaul, a 3D space game whose server is Zig: its world sealed and verified green
- orchard.encroe.testnet
Orchard, a farm game whose server is Go: its world sealed and verified green
- encroe-ember-3924.testnet
Embergate's played world: sealed, verified green, checked by its own players
- encroe-kill-beaa.testnet
Killed from this site: a visitor's click released it, the browser brought it back
- encroe-kill-827e.testnet
A silent studio: released by a stranger, revived and played on in a browser
- encroe-life-52e4.testnet
The first full life: a broken build caught red, the real one green, the studio's silence, the release
Five languages, one verifier
Rust
Embergate
core 49ff0c57f10f…
released · green
C++
Matchday
core f149751774f7…
released · green
C
Neon City
core 3f4a1e626aa6…
released · green
Zig
Starhaul
core f8a50a172e7d…
live · unverified
Go
Orchard
core 91665f535afb…
live · green
Rust, C++ and C: sealed, released, revivedZig and Go: sealed, verified green
Before any of this
Four go/no-go experiments decided whether Encroe could exist at all. All four passed on testnet.
- E1The key exists only in NEAR's MPC network, and is released publicly once the studio's heartbeat lapses
- E2Only the pinned verifier, run through the contract, can read the studio's secret: a thief build and a direct call were refused
- E3The enclave's TDX quote verifies against Intel's collateral, bound to the exact input and output
- T1The contract accepts a run only after NEAR's own DCAP verifier checks its quote; a replayed quote is refused
What you trust →
Each part of Encroe, what you have to trust about it, and how to check it yourself.
The threat model →
Who could cheat, how, and what stops them; and what is out of scope.