how to audit us

The ledger, and how to catch us lying.

Every submission and every verdict is an entry in one append-only, hash-chained ledger. Corrections are new entries; edits are impossible without breaking the chain in public. The chain head below is signed by the node key and re-stamped on every append.

To audit: record today’s head. Tomorrow, fetch the chain and confirm today’s head still appears in it, at the same index, with the same hash. If it does not, we rewrote history, and you have the signed proof.

Our own database cannot help us cheat: it holds only projections, and a standing job rebuilds it from the ledger and content-addressed store, then diffs. Drift is an alarm, not a shrug.

Static audit snapshot

Bundled at build, no JavaScript required. Download the chain segment and re-derive every entry hash and prev-link yourself; the head below must be the last line’s entry_sha256.

entries3,228
headfcc815ff5b45eb268da0ecdae9579dd96805b18a98b4f3289a9f1f805d5df067
prevc536d37437ce89a23cc2287de9ca6a4969d15ac5ca7c510bf0de6907f481d84b
chain sha8fddb9338151c49962bde67cba95630308c00f92a6c2af4d0ec80e1805542f1c

Node public key and detached head signature attach when the live node is connected (below). The chain itself is verifiable from the segment alone today.

Live signed head

fetching the signed head…