Forensic Provenance Ledger
Current anchor
Not verified—- Records
- 0
- Bytecodes
- 0
- Reports
- 0
- Findings
- 0
- Capsules
- 0
Ledger
Keep a tamper-evident, hash-chained record of your analysis artifacts so you can prove nothing in the evidence trail was altered later.
| # | Kind | Label | Content hash | Recorded | Chain link |
|---|
Simulate a Tamper
Mutate a record's content hash in your local copy of the ledger to see the verifier fire. The chain link stays stale, so Verify chain reports the first broken index and the expected vs. actual link. The server ledger is never modified — reload the page to restore the pristine chain.
Anchor artefact
How the Chain Works
- Each record stores
sha256(prev_link || content_hash || kind || label || recorded_at)as its chain link. - The genesis record chains from
0x000…000(64 zeros). Mutating any single record — content, label, kind, or timestamp — changes the expected link at that index and every subsequent index. verify()walks the ledger, recomputes each link from the prior record, and returns Intact (with the final anchor) or Tampered (with the first broken index and the expected vs. actual link).- Records are anchored server-side in durable, append-only storage. This page fetches a copy and runs verification in your browser with the platform's native SHA-256 primitive — the same hash formula as the backend — so you can check the chain independently of the server that produced it. The tamper drill above mutates only your local copy.
Sign in to view the Provenance Ledger
Use the Sign In button in the navigation bar.