[ CHRONEX_TERMINAL ]

Chronex audits autonomous agents that spend money on Robinhood Chain. An agent is handed a mandate — one asset, a spending cap, an expiry, a list of approved payees — and then it acts on its own.

Chronex replays the chain’s logs, sets what each agent actually did against what it was authorised to do, and publishes the result with the evidence attached. It is not an alert feed. It is an audit anyone can run again and get the same answer.

Every finding is derived from eth_getLogs. Nothing here reads contract state.

That is not a shortcut — it is the constraint that makes the output checkable. This chain’s public RPC is not an archive node: a historical eth_call or eth_getCode comes back metadata is not found. A tool that leaned on archive state would emit claims nobody else could re-derive.

Logs are different. They are served in full from block zero by a free public endpoint that answers the same query for anyone who sends it. So every number on this console can be reproduced by anyone, on the same endpoint, with the commands in DOC_05.

Chronex is not handed a list of addresses. It filters the whole chain on the topic0 of GrantIssued and takes whatever answers. On the current index that returned three vaults, never published anywhere as a set.

Eight further contracts matched on Swapped alone. That signature is an ordinary shape for any swap contract, and on this chain it has been emitted since block 10,604,012 — long before the first vault existed. All eight were rejected. Nothing is counted as a subject until it emits GrantIssued, whose uint48/uint32 layout belongs to this vault design and little else.

Subjects are found, not supplied.

Most flags carry the indices of the events they were derived from, and every index resolves to a transaction you can open. A few rest on something that never happened instead: an empty payee allowlist is established by the absence of a MerchantAdded event, and an absence has no transaction to point at.

Those ship with an empty evidence list rather than a citation that would not survive being checked. What Chronex will not publish is a finding resting on neither — not an event, not a documented absence, just a view.

You do not have to trust this page. Every command below is sent to the same free public endpoint Chronex uses, and hands back the raw data these findings were built from.

That endpoint is shared and rate-limited. The first command walks the whole chain, so it can answer 429 Too Many Requests or context deadline exceeded under load. Neither is a wrong answer — wait a moment and run it again.

Each subject reduces to one document and one hash. The document below is the exact text that gets hashed, printed in full — nothing is summarised or abbreviated for display. Recompute keccak256 over it and you get the hash beside it, byte for byte.

The format is line-based rather than JSON on purpose: key order and whitespace differ between languages, and either would silently change the hash. Lines are joined with , no blank lines, no trailing spaces, addresses lowercased, findings sorted by their own line text, and a finding with no event evidence carries - in its last column.

This is what an attestation signs. The registry contract that will carry these hashes is written and tested — the whole flow has been run end to end against an in-process EVM with the archive above, and it has not been deployed to a public chain. Until it is, the hashes below stand on their own: they can be recomputed from this page without asking any chain, and any edit to the archive parts them.