Every claim hash-chained. Paste a receipt, get the evidence chain back.
Chain integrity
chain verified
11 receipts on chain
Every ingested observation is appended to an Ed25519 hash-chain. Each receipt’s prev field is the hash of the receipt appended immediately before it, so altering, deleting, or reordering any stored record changes the hash of everything downstream. ledger.verify() walks the whole chain and flags the first broken link.
Verify a receipt
Paste a receipt hash from the table below — or from any Wall item, brief, or profile across the platform — to trace it back through its evidence chain.
Evidence chain for 76d6adda01a4936631… — the claim first, then every parent it was derived from, back to source observations.
source Global Incident Map · reliability C (Fairly reliable) · Port-side infrastructure advisory
How a conclusion chains back to its evidence
Raw observations are appended with ledger.append(payload) — each gets a receipt with no parents; it is the source. When a surface produces a derived claim from evidence — One Query (02) merging a cross-referenced profile, Brief (09) writing a situation report — it calls ledger.derive(claim, parentHashes). The new receipt’s parents field lists every receipt it was built from, so tracing a brief’s hash walks back through each parent to the source observations that justify it. Nothing ships as fact without a traceable path back to a receipt.