The Trust Anchor Protocol · in your browser

Don't trust us. Verify us.

A GATE ledger is only evidence if you can check it yourself. This tool recomputes the hash chain and Merkle root and compares them to externally-anchored checkpoints — entirely in your browser. Nothing is uploaded anywhere.

Paste a ledger export and its anchored checkpoints, load the sample to see the mechanism, or pull Claire's own live record and read the external witness for yourself. A clean ledger verifies; alter any past decision and the check fails against the checkpoint an external notary recorded before the change. That's the difference between a log you're asked to trust and a record you can test.

What this proves — and what it doesn't

A pass means the ledger you hold matches the head and Merkle root that an external anchor recorded — so nothing before those checkpoints was deleted, backdated, or softened without detection. It does not, by itself, establish that the anchor is trustworthy or that the ledger is complete; those come from the anchor's independence and the checkpoint cadence. Tamper-evident, not tamper-proof — and honest about the difference. The full protocol is documented in the Trust Anchor Protocol spec.

One decision · a receipt

Verify a single decision

A receipt from /api/receipt proves that one sealed decision sits inside a checkpoint root an external notary witnessed — without revealing any other decision. Paste a receipt (or load the sample) and check its Merkle path to the witnessed root, entirely in your browser.

Why a receipt matters

The ledger check above proves the whole record is intact. A receipt proves a single decision to a third party who should not have to see the rest — an examiner asking "prove this approval," a counterparty verifying one action. The proof is content-free (hashes only) and checks offline: recompute the path to the root, confirm it equals the checkpoint an external notary timestamped, then verify that notary's token yourself. Tamper-evident, not tamper-proof.