THE ARCHIVE CANNOT LIE TO YOU.
Every call this site makes cites a document in our archive. This page is how you know that archive is what it was — that nothing was inserted, edited, or deleted after the fact. You don't have to trust us; you can check.
The mechanism
Every document is fingerprinted on arrival. Each fetch is stored raw with its URL, UTC timestamp, and SHA-256 hash. Change one byte later and the hash no longer matches.
Every night, one root covers everything. All fingerprints are combined into a single Merkle root — one 32-byte value that commits to the entire archive. Any altered document produces a different root.
Each seal contains the last one. The night's root is hashed
together with the previous night's seal: seal = sha256(previous_seal + merkle_root). Rewriting
any past day would change every seal after it.
The seal is written where we can't touch it. Each seal is posted as the calldata of a transaction on the Base blockchain. The block timestamp is set by the network, not by us — from that moment, the archive's shape at that instant is public record.
Every seal ever made
| № | Day (UTC) | Documents | Seal (SHA-256) | Base tx |
|---|---|---|---|---|
| 3 | 2026-08-26 | 10,156 | 67134e58f0f5c74972e17d9418124643bb0191aa146a0d768037b9f1b5132b36 | 0xae48cd1fd7e0… ↗ |
| 2 | 2026-08-25 | 7,915 | 4d332b674d26fd0ba57936539b42fddaeb69a87928daa4a64f13a531d978bb86 | 0xc63d7fef0003… ↗ |
| 1 | 2026-08-24 | 1,202 | 64571969278a2a363cb8c5f27119b2db881c7a5c7a5b424488d57b13b6162e8f | 0x6a6657279b57… ↗ |
What a seal proves — and what it doesn't
It proves the archive existed in exactly this form no later than the seal's block time. Because each seal chains to the previous one, the newest transaction on Base seals the entire history before it. We cannot backdate a catch, quietly fix a miss, or slip a document into the past without breaking a chain that's already public.
It does not prove our calls are right. That's a separate, equally public test: every call is graded against the venue's official settlement in the ledger, and misses stay up.
Checking it: open any seal's transaction on BaseScan — the input data is that day's seal, byte for byte, matching the table above. For a specific disputed document, we produce the Merkle path from that document's hash to a sealed root, so anyone can replay the arithmetic — no access to our systems required.