Evidence, not screenshots

Every claim, checkable.

Each block below is the contract's own NEP-297 event, fetched live from its transaction record on an archival node. Nothing here is a picture of a result.

Five recorded transactions reading chain…
Verify it yourself

Three commands, nothing installed.

Python's standard library only — no packages, no wallet, no account.

Read

27 read-only checks: each agent holds exactly one restricted key, the policy is live, the vault holds the stablecoin it governs, and the five transactions say what this page says.

$ python3 scripts/verify.py 27 passed, 0 failed

Attack

Nine signed attacks with the agent's real key, then one legitimate payment. Exits non-zero if any attack gets through.

$ python3 scripts/redteam.py 9 of 9 attacks stopped

Test

40 unit tests on policy and authorization, and 14 sandbox tests that settle real transfers and callbacks on a local NEAR node.

$ cargo test 40 passed · 14 passed
The key in the repository

One private key is public, on purpose.

It is the agent's restricted key. verify.py scans the repository, confirms it is the only private key present, derives its public half and checks that it is the sole key of aa-agent.testnet on-chain.

5. The private key published in this repository PASS exactly one private key is present in the working tree PASS it is the sole key of aa-agent.testnet, the one restricted to the vault