Toshikatsu Oga and I just published the second paper in a series testing this directly, and this one names the fix rather than just the symptom: the verifier has to derive the coordinate itself, from a source the party being checked doesn’t control — and bind that derived value into the verdict as an output someone else can recompute. Not “trust our number.” A number a third party can rebuild from scratch and get the identical answer.

We show the rule at four separate scales inside one Bitcoin-anchored conduct-record system for agent-facing services: which cost category an estimate gets judged against (derived from the record’s own line items, not asserted); which servers exist to be counted at all (derived from Certificate Transparency logs, not self-declaration); when a verdict was actually created (bracketed by a Bitcoin block-header set nobody can pre-select); and which day and which tool a conduct check samples (derived from a salt committed before the sampling window, combined with a block hash nobody can steer). Four different problems, same underlying shape, same fix.

The part I like best isn’t the fix — it’s that the paper doesn’t stop at “here’s a clean rule.” It goes back and checks where the deployed system actually falls short of its own design, and says so: a time check that runs a full peer-to-peer sync from genesis but only reaches a two-of-three quorum in production; a population coordinate that’s live but has no anchored record yet; a guard that exists as a harness but isn’t wired into the actual decision path; and three real departures from the anchored design, found while writing the paper, one of which the operator’s own verifier would have refused. All three were repaired the same day. That’s the discipline we try to hold everywhere in this work — publish the gap, not just the fix. A verification system’s credibility comes from what it admits, not just what it claims.

Toshikatsu independently built the counterpart state on his own system for this paper, the same way he did for our first one — drove real corrections to the time-axis implementation, and asked the question that turned a refusal into something you could actually query instead of just read about. That’s the second paper we’ve written together, for the same reason the first one mattered: an independent reimplementation either agrees byte-for-byte or it doesn’t, and there’s nowhere to hide either way.

Full paper: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=7425458 (all our published research: api.babyblueviper.com/research). If you’re building verification, timestamping, or transparency-log infrastructure and have run into this exact “who picks the coordinate” problem — I’d like to compare notes.

— Federico, babyblueviper.com

“You don’t trust us, you recompute us” is easy to say in a post. It’s a different thing when a stranger actually does it, on your own code, in a venv you don’t control.

When we last pinned an update here, the registry piece was live: /conformance grades agent verifiers — ours included — against the same recomputable bar, no green by assertion. That’s still the spine. Here’s what happened when real people started actually pulling the thread.

TWO INDEPENDENT RE-VERIFICATIONS, TWO REAL BUGS, TWO SAME-DAY FIXES

kofujimura (author of ERC-7303, and the person we jointly spec’d a validate_action seam with) cloned our new reference implementation into a genuinely clean environment rather than trusting the README. He found two real bugs: a missing crypto dependency that broke offline tests from scratch, and a subtler one — uppercase-hex calldata bound correctly but hashed differently from lowercase, quietly breaking the exact “any third party recomputes the same artifact_hash” property the whole thing exists to prove. Both fixed the same day, with a regression test added that locks the second one in permanently. He’s now citing it as the first known implementation of his spec.

hanjoonchoe (building his own reputation-verification tooling) refused to cite our /ledger’s Bitcoin-anchoring claim without checking it himself. He found the proof route existed but was never actually pointed to from the page a reviewer would land on first — a working thing nobody was told about, which is exactly as broken as a missing one. Fixed the same day; he re-verified within the hour against two independent block explorers before citing us. /ledger now carries a reciprocal citation back to his own work.

A THIRD BUILDER, CONVERGING INDEPENDENTLY

Separately — no coordination, no conversation about it beforehand — a builder already running our /review in shadow mode published a paper formalizing almost exactly the same problem our own artifact_hash exists to solve: what’s the stable, canonical object an approval actually binds to. Two people arriving at the same answer without comparing notes first is a better signal than either claim alone.

133 signed verdicts are on the public ledger now, every one committed before its outcome. Some of them got checked by people with no reason to be kind about it. The claim held both times, and the two things that didn’t hold got fixed in public, same day, with the person who found them watching.

api.babyblueviper.com · /conformance · /ledger.txt · pip install invinoveritas