Mainnet
What has really run on NEAR mainnet, read from files published with this site. If a number is not in a file, it is not here.
Looking for a published mainnet run…
Track by track: testnet and mainnet
“Verified on testnet” links to recorded, explorer-checked runs. The mainnet column is computed from the published mainnet run file and says “pending” until it exists.
| Track | On public testnet | On mainnet |
|---|---|---|
| Social Money | verified DAO votes, funding transfer, reputation | pending |
| Autonomous Business | verified chunked execution, crash-restart, DAO cancel | pending crash-restart and cancel were not run on mainnet |
| AI Security & Defense | verified three layers, red team, protocol probes | pending OutLayer wallet policy and the red team were not run on mainnet |
| Privacy & Private AI | verified TEE-parsed intent, signed and attested | pending hidden execution is not claimed anywhere |
| Real-World Money | verified payouts, fee, returns (play money) | pending |
| Open Innovation (sealed) | verified commit-reveal mandate | not part of the mainnet slice sealed mandates are not part of the mainnet slice |
| Unstoppable DeFi | verified Ref swaps; Intents quoted only | pending Intents settlement is a separate owner-run script and has not run |
What is ready, and what it will cost
- One atomic transaction deploys and initialises the contract, so nobody can initialise it first; rehearsed on testnet.
- A read-only preflight checks the network, owner, key, balance, target accounts and the wasm hash before anything is sent.
- Read-only verification and a JavaScript contract test check the deployed contract against the committed wasm.
- The owner moves about 15.15 NEAR into accounts it controls (measured gas about 0.07 NEAR); the mandate sells at most 0.6 NEAR (about US$2).
- On mainnet the vault is a key held by the worker and the council accounts are controlled by the authors: stated on every mainnet claim.
Details: deployment plan · how to run it.