Chain verification · client-side · no server involved
Don't take our word for it. Recompute the chain.
If a record was edited after signing, the recomputed hash will not match the stored one — and that row is reported as BROKEN, visibly, with the row identified. The button below proves it, including what happens when a record is deliberately tampered with.
Verify a chain
The verification runs locally in your browser using WebCrypto. No record leaves your machine. Today the chain is sha256-linked; the verify button only ever claims what the cryptography currently does.
Published chain status
The status of the production chain as published by the instrument. The button above recomputes the public replay set independently — the two never have to take each other's word.
Records are sha256 hash-linked for tamper-evidence and signed with Ed25519, anchored with OpenTimestamps — a ~3KB card verifiable offline against the published key f4b4278d… (did:web:csoai.org). The post-quantum ML-DSA-65 (FIPS-204) signer is built, not shipped; the label will name it in the same commit it ships.
Last record: DR-0034 — An SSM leg breaks the dead-weight regime (n_eff > 2.0)
What this button does NOT do
- This button recomputes the sha256 hash chain — tamper-evidence, not authorship. Authorship is carried by the signed card: a ~3KB measurement card signed with Ed25519 and anchored with OpenTimestamps, verifiable offline against the published key
f4b4278d…(did:web:csoai.org). The post-quantum ML-DSA-65 (FIPS-204) signer is built, not shipped; the label will name it in the same commit it ships — never ahead of it. - It does not contact a server. Verification is local; you bring the records and the WebCrypto implementation in your browser.
- It does not assert that a model is "safe", "compliant", or "authentic". Those words are not in the button's vocabulary, on purpose.