Paste a receipt reference. This page fetches the live public audit chain and
re-walks the SHA-256 hash-chain links in your own browser with crypto.subtle —
the linkage is re-walkable client-side; you run the check, not us.
Authorship of each row is operator-attested (HMAC-sealed server-side), so we say plainly which part you prove and which part you trust.
chainlink_prev must equal the prior row's chainlink_row — pure SHA-256, no trust). The row leaf contents are withheld, so leaf integrity and authorship are operator-attested (server recompute + per-row HMAC seal). We do not claim the rows are stranger-reproducible from scratch.0xa938754d9a9b6ec2f4533ddbc0fdade7fc2eb80b) — read a given night’s committed head by calling getAnchor(unixDay) on that contract (unixDay = floor(unix seconds / 86400)); a non-zero return is the anchored head SHA for that day, so altering sealed history would mismatch the public on-chain anchor. Earlier days (before the cron went live) are not back-anchored, and rows added since the last nightly anchor aren’t anchored yet.A receipt is one row in the public chain. It references the row's
chainlink_row hash. Paste a chainlink_row from the live chain, or just
use a sample — either way we re-walk the live chain and locate it.
crypto.subtle. The spot-check asks the live endpoint to recompute one row's leaf — that part is operator-attested, and we say so.# This terminal shows real responses from ironbridge.foundation/api/law25/verify # The re-walk runs locally with your browser's crypto.subtle — nothing is taken on trust.
chainlink_prev equals the previous row's
chainlink_row, and that the server's reported head matches the row we walked to. A clean
re-walk proves the visible chain is internally continuous — no row was inserted, dropped, or
re-ordered without breaking a link. What this does NOT prove on its own: that any payment cleared
(that is an assertion in the row — check the txHash on Base yourself), and that the withheld leaf
contents are authentic (see below).?row=N) — but that recompute happens on our server, so it is attested by us, not
reproduced by you. We label it operator-attested and never call it stranger-reproducible.