Audit-of-record ledger

Chain head

Entries

687

Head hash

80f656c7d8085f903a3750af97f35d85227fdac185839c8eb3a171b3115c9382

Last entry

#6874 · review · 2026-10-07T01:56:23.646212+00:00

How an examiner verifies independently

1. Export the carrier's ledger (seq, ts, kind, ref_id, payload_hash, prev_hash, hash).
2. Confirm the first entry's prev_hash is sixty-four zeros.
3. For each entry, recompute SHA-256 of 'prev_hash|ts|kind|ref_id|payload_hash' and compare with hash; confirm prev_hash equals the previous entry's hash.
4. For any assessment, canonicalise its full stored JSON (sorted keys, no whitespace), hash it with SHA-256 and compare with the ledger's payload_hash for that assessment (the case-file view is an excerpt; request the full record).
5. Canonicalise the transaction revision the assessment names and compare its SHA-256 with the assessment's input_digest: a changed input fails here even when the assessment is intact.
6. Compare the head hash and entry count with a checkpoint you retained earlier (for example from a previous pack); a shorter or different chain means truncation or replacement. RegBench does not yet publish an external anchor.

Verification as JSON