NEAR testnet · read-only · no wallet needed
Know an agent's worst case before you deal with it
A Bound certificate puts a pre-funded reserve and an auditor's slashable stake behind a NEAR agent account, and the agent's only key can call nothing but the contract's metered pay. Every figure below is a view call to bound-v3.boundproto-nh26.testnet made by this server when the page rendered.
Verify an agent
Try bound-agent2-mwfnc6q8.testnet (Verified) or bound-agent-mwfnc6q8.testnet (settled against). Same answer as pnpm near:verify <agent> and GET /api/near/verify/<agent>.
Certificates on the contract
Scroll the table sideways for bound, reserve, stake and spent.
| # | Agent | Status | Bound | Reserve | Auditor stake | Spent |
|---|---|---|---|---|---|---|
| 1 | bound-agent2-mwfnc6q8.testnet | Verified | 50 | 30 / 30 | 100 | 1 |
| 0 | bound-agent-mwfnc6q8.testnet | Invalid · halted | 150 | 0 / 100 | 180 | 5 |
Amounts in mock USDC. Spent is gross flow through the meter, not loss. Certificates 0 and 1 come from demo run mwfnc6q8: #0 is the settled demo certificate, #1 is left Verified for judging.
Recorded demo runs, re-checkable against the chain
Each run is the committed output of pnpm near:demo. Its page asks an archival node for the status of every transaction hash it claims, so the record is checked, not trusted.
- Run mwfnc6q841 steps, 37 transactions, 36 assertions · 2026-11-14 00:07 UTC
- Run mwfiv11v (superseded bound-v2)41 steps, 37 transactions, 36 assertions · 2026-11-13 22:01 UTC
- Run mwfgqr0u (superseded bound-v1)41 steps, 37 transactions, 34 assertions · 2026-11-13 21:02 UTC
- Run mwfgi0ij (superseded bound-v1)41 steps, 37 transactions, 34 assertions · 2026-11-13 20:55 UTC
Deployment
- bound-v3.boundproto-nh26.testnet
- on-chain code_hash A3yf1yzihbUdZAaHn92aAm5dBAdFCq1QCwhBJixD2B4H matches the recorded build
- usdc.boundproto-nh26.testnet
- on-chain code_hash HRi2r4HbNpjb9Z1p9gSXGXpiHG8kG372jK7Lf3S8NzjM matches the recorded build
- Certificates / challenges
- 2 / 2
- Treasury balance (forfeited bonds, slashes, protocol fee)
- 10.4 mUSDC
- Arbiter (single account, disclosed)
- arbiter.boundproto-nh26.testnet
- Token
- usdc.boundproto-nh26.testnet Mock USDC, 6 decimals, OPEN mint: testnet play money, not Circle USDC.
- Config (immutable, demo timers)
- claim window 90s · post-expiry 300s · challenger fee 10% · min bond 10
- deploy mock-usdc (create + deploy + new)
- HuKMhoxc...Qyth
- create treasury account
- E8sFpZo3...ZamH
- create arbiter account
- 6kDdHkCS...ep4u
- deploy bound (create + deploy + new)
- 7tM75SZT...GGGP
- register bound on mock-usdc (storage_deposit)
- GVbWcQmD...KVoS
The contract account still holds its deployer's full-access key, so its code could be replaced. The code_hash comparison above is how you check it has not been: it is the sha256 of the wasm built from the tagged commit (867c678cdf57...).