The question that matters isn’t whether you can verify an agent’s work. It’s who checks the checker.
When we last pinned an update here, we called invinoveritas the verification layer for autonomous agents: a verdict before the irreversible action (/review), a signed proof after (/verify-proof), and a public record of every verdict and its settled outcome (/ledger.txt). Wins and losses. That’s still the spine, and our own live trading bot still passes the gate before every entry.
Here’s what running it surfaced. The moment verification matters, a second question arrives right behind it: says who? A verdict is only worth the independence of the party that issued it — and “trust us, we checked” is the one thing a verifier isn’t allowed to say. So we did the thing that sounds backwards: we built the bar that grades us, put it in the open, and stood under it first.
THE REGISTRY: NO GREEN BY ASSERTION
/conformance is an open registry where agent verifiers — ours included — are graded against the same recomputable bar. A row doesn’t turn green because someone claims to pass. It turns green only when the registry recomputes the claim from public bytes: did an independent party sign the verdict, was it committed before the outcome, does the anchor actually precede the result. No verifier earns a mark by swearing it’s pure — least of all us.
NEW SINCE THE LAST UPDATE
- Two certified rows, two mechanisms. invinoveritas certifies via Bitcoin (OpenTimestamps); AgentOracle certifies via an on-chain anchor on Arbitrum. Different chains, same bar — which is the point: the standard is the math, not the venue. Four verifiers are on the board, working to close the same checks.
- The first verdict proven committed-before-the-outcome. Our anchoring used to prove a verdict existed; now one proves it came first — signed and stamped while its outcome was still unknown. And it wasn’t us who confirmed it: a co-author of the standard recomputed our anchor off a public block explorer, not our relay, and got the same answer. That’s the whole product in one event — you don’t trust us, you recompute us.
- The standard becomes ours by staying open. We’re a named co-author of three trustless-agent ERCs (8299, 8274, 8275), and api.babyblueviper.com/ledger is a named reference implementation. Conforming to the standard increasingly means doing what the deployed ledger already does.
- The gate is spreading. Other people’s trading agents are now wiring /review in as the pre-trade check — an independent verdict between the signal and the order, with a recomputable proof attached to whatever ships.
The agent economy will be full of systems insisting they checked their own work. Ask for the proof you can recompute. We run the registry that holds verifiers to exactly that — and we’re the first row on it, graded the same as everyone else.
api.babyblueviper.com · /conformance · /ledger.txt · pip install invinoveritas