Interactive · runs entirely in your browser

The Forensic Fabric. Walk it, verify it, then break it.

Below are 12431 real records from the Forensic Fabric — a running, tamper-evident ledger of 42,667 entries. Press Verify and your browser will recompute every hash with Web Crypto and check that each record links to the one before it. Then press Tamper, change a value, and watch verification fail at exactly the record you touched.

Nothing here is a screenshot and nothing is taken on trust — the page ships no pre-computed answers, and you can read the source.

Idle — press “Verify the chain”.

The Forensic Fabric

Each record carries the hash of the one before it

That is the whole idea, and it is a fifty-year-old idea: change any byte of any record and its hash changes, which breaks the link the next record depends on, and every record after it. Tamper-evidence falls out of the arithmetic — nobody has to notice.

Summarising many records into one

Merkle tree over the same records

Click any leaf to get its inclusion proof: the short list of sibling hashes that proves that record belongs to this set, checked against a root recomputed live. This is the standard construction — the same shape of proof a transparency log or a blockchain uses.

Built from

Standard, checkable primitives

Every component is a published standard. None of it is proprietary, and that is the point — cryptography you cannot inspect is cryptography you should not trust.

Ed25519
RFC 8032
per-hand digital signatures on every unit of work
IN USE
SHA-256
FIPS 180-4
the append-only hash chain that makes tampering detectable
IN USE
Merkle trees
Merkle, 1979 — public prior art
summarising many records into one verifiable root
IN USE
SLIP-0010 / BIP-39
SLIP-0010 hierarchical deterministic derivation, Ed25519 form
deriving per-identity signing keys from a single vaulted seed
IN USE
ML-DSA
FIPS 204 (NIST post-quantum signatures)
hybrid post-quantum signatures alongside Ed25519
SCHEMA-READY
Append-only ledger
write-once/WORM discipline
history that can be added to but not rewritten
IN USE

About the data on this page

These records come from the running custody ledger. Internal file paths and shard identifiers are redacted, and each entry_hash is recomputed under the same canonical rule after redaction — so every hash shown is the hash of the record shown, and you can verify all of them yourself in this page.

What this page does not show

How the system combines these parts, and how its agents coordinate at scale without a central coordinator, is the subject of an in-preparation patent application and is deliberately absent. What you can see here is the craft — standard cryptography, applied correctly, and verifiable by you.