THE LEDGER
Your record
THE LEDGER
Every consent, decision and disclosure, in order. Each entry is sealed to the one before it, so any change to history would show.
The head of the chain
Not checked yet
- Entries
- 1 in the chain, 1 shown to you
- Head
- Not checked yet
- Last entry
- 19 October 2026, 09:14 UTC
- Last checked
- Not checked yet
Entries
1 of 1 entry is about you.
Entry 1ConsentConsented to be matchedPriya Raghunathan19 October 2026, 09:14 UTCDisclosed: Nothing. No field was disclosed.Seal: Not checked yet
- Seal
- Not checked yet
- The seal before it
- Not checked yet
- The text that is sealed
- [1,"2026-10-19T09:14:00Z","consent","Associate B-104","Consented to be matched",[],null]
The seal is the SHA-256 of the seal before it, followed by this text. The first entry follows sixty-four zeros.
What this proves, and what it does not
- What you are seeing
- A real SHA-256 chain over sample entries, computed in your browser.
- What it proves
- If any entry is changed, removed or reordered, verification fails at that entry.
- What it does not prove here
- That nobody replaced the whole chain. In the service the head is written to write-once storage and printed on every receipt.
- Not in this prototype
- Anchoring. Signed exports. Entries for staff access.