For studios
Make your game outlive you.
Put your server in escrow on NEAR. While your studio lives, nothing changes for you. If it ever goes quiet, the game goes to the people who played it, with everything they earned.
A promise you cannot break
Players buy a game that cannot be switched off for good. The escrow says so, and NEAR enforces it.
Proof, not a policy page
Anyone can check your sealed build is real without opening it, and every player can check their items are inside.
Costs almost nothing
5 NEAR of storage once. A heartbeat is one transaction. Verification is paid by whoever asks for it.
5 escrows created through encroe.testnet · the directory
Four steps, then nothing.
- 1
Create your escrow
From your wallet, above. It is born keyless: nobody, including you and us, can ever change its rules.
- 2
Compile your server core
Your game's rules and players' state, built to WebAssembly with no imports: Rust, C++, C, Zig, Go, or anything that targets wasm32. Then drop the .wasm into the core checker.
# Rust cargo build --release --target wasm32-unknown-unknown # C++ (C: zig cc, -std=c11) zig c++ -target wasm32-freestanding -O2 -g0 -nostdlib \ -Wl,--no-entry -Wl,--strip-all -o core.wasm core.cpp
Check your core in the browser · all build recipes - 3
Seal your live world
From your browser: drop in your core and players file, and your wallet signs three times (the key row, the commitment, the verification). The enclave checks the sealed build and NEAR checks the enclave. Or let a scheduled job run the same steps:
ESCROW_ACCOUNT=your-game.encroe.testnet ESCROW_NAME=your-game \ ENCROE_GAME_URL=https://your.game scripts/studio/bot.sh seal
Seal from your browser - 4
Keep your heartbeat
A scheduled job sends it and re-seals your world, so your players' newest items are always inside. Stop it, and after your grace period the game is theirs.
The workflow