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

Five languages, one verifier

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.

GO_NO_GO.md

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.