06 / 07
Security
Wallets, games, builds and money are kept apart, so that a problem in one cannot reach the others.
Your wallet
- Connecting asks for one signed message. It proves the wallet is yours; it moves nothing and approves nothing.
- Only a launch asks you to sign transactions, and you see them in your wallet before you sign.
- Games never see your wallet. They cannot ask it for anything.
Games
- Every game runs on a separate domain inside a sandboxed frame. It cannot read the platform's pages, cookies or storage.
- Games cannot make network requests, open other sites, or store anything in your browser. The acceptance test checks this on every build.
- A new version only replaces the live one after it has passed every check.
Builds
- Each station runs on its own short-lived machine and can touch only the files of its one game.
- What launchers, creators and players write is treated as a description of the game and nothing else. The agent has no shell and no network, and every file it touches is checked to lie inside its workspace.
- Blender scripts and multiplayer server code run in a sandbox without network access.
Money
- Each coin's fees gather in that coin's own vault. Its key is stored encrypted and is used only for fee collection and released payouts.
- Every amount that enters or leaves a coin's books is listed in its Budget tab.
- Prizes are only paid for runs the platform has replayed itself, or for results its own room servers decided.