Black box verifier

Recomputes the hash chain over an AI agent's decision records in your browser and compares it with the head anchored on NEAR. Try the agent's pre-sign gate on a payee of your choice (section 7).

agent

…

final head

…

1. Chain over data/records.jsonl

Check another copy of the records (for example one you edited) against the same checkpoints:

The checkpoint heads come from this repository. On their own they only show that the file is consistent with itself; the NEAR anchor below is the independent check.

2. Head anchored on NEAR (SocialDB)

3. Append-only registry (NEAR contract, locked)

A contract with no access keys and no delete or edit method: once a head is in it, nobody can change or remove it. Its code hash must equal the reproducible build in contract/.

4. Coverage: wallet transactions vs records

Every transaction the agent wallet sent should belong to a record (its own tx hash, or a recorded mint/crank batch). Reconciled by node src/coverage.mjs; the live nonce is read from Robinhood Chain.

5. Where the money went: gated sends read back from the chain

The pre-sign gate believes what the agent's code tells it, so each cycle reads every gated send's transactions back from the chain (and, for a NEAR deposit, 1Click's own record) and checks where the value actually went. Written by node src/flows.mjs --write into data/flows.json; this page shows that committed result.

6. Last 50 decisions

Newest first, simulations folded below the list. Transaction links open the Robinhood Chain explorer; ✓ means node src/rh-proof.mjs --all found the receipt and it was sent from the agent wallet.

7. Try the gate

The agent's own pre-sign decision (src/gate-core.mjs), run in your browser on the published policy, these records, the newest registry anchor, the shared blocklist and the payee's code read from its chain. It judges the description only: the agent's wrapper also shows it the unsigned transactions.

Try: