[ 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. A contract is only counted as a subject when it emits GrantIssued, whose uint48/uint32 layout belongs to this vault design and little else.

Subjects are found, not supplied.

Every flag carries the index of the events it was derived from. A finding without a transaction behind it is an opinion, and Chronex does not publish those.

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.