type html> The Blackbox Archive
RECOVERING
BlackboxArchive

What did the
agent do?

A forensic record of what autonomous agents actually did on chain — not what they were told to do. Every mandate, payment and trade is recovered from the chain’s own logs and published with the evidence attached.

READ THE RECORD
SUBJECT INDEX

FIELD 01

THREE RULES

Nothing here is taken on trust, including this page.

01

Logs only, never state.

This chain’s public RPC is not an archive node — historical state calls fail outright. So every finding is derived from eth_getLogs, which means anyone can reproduce the whole analysis with one public endpoint and no credentials.

NO ARCHIVE NODE· NO API KEY
02

Every finding carries its evidence.

A flag names the exact events it was derived from, and every event links to its transaction. An accusation without a clickable receipt is not a finding, it is an opinion.

03

The watcher holds nothing.

No contract, no keys, no custody, no write path to any chain. The archive can be wrong about a vault; it can never cost anyone money by being wrong.

READ ONLY· ZERO CUSTODY
FIELD 02

HOW IT WORKS

Four steps from a raw log line to a published record.

FETCH

01LOGS

Full range, block zero to head.

DECODE

02ABI

15 events, selectors computed locally.

ANALYSE

03RULES

10 forensic rules, each citing events.

PUBLISH

04DOC

One static file, no database.

FIELD 03

MANDATE REGISTER

What each agent was authorised to spend, and what it has spent.

FIELD 04

FINDINGS

FIELD 05

RECOVERED LEDGER

Agents can lie.
Logs cannot.

Point the recorder at any vault address and it will read that vault’s entire history from the chain, apply the same rules, and publish the same kind of record — whether or not the people who deployed it want one.

RUN IT ON A VAULT