RESOLUTIONWIREdocuments decide markets

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

01

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.

02

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.

03

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.

04

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)DocumentsSeal (SHA-256)Base tx
14 2026-09-07 87,615 96abe766327df293e232062bc066c02a90f687259b7d09aed4f38c342bea329f 0x48b2efcb7985… ↗
13 2026-09-06 76,702 5718fbaed8f7691ee3e06e3e101010cbd80b776f39900d40e5c3e305a79fc813 0x3617c4e0d09d… ↗
12 2026-09-04 69,005 d3465a10bfe336b8ad02489dc521c20c0d5d1ba7237e97e4b1cb3bc7674d7e27 0x639f36b87234… ↗
11 2026-09-03 61,534 a29a12940eb53590f2141ea63fe7c1c04324e1a01be2ce1c1ab18d392fd32d9d 0x6b90fd09f625… ↗
10 2026-09-02 54,226 2c8b5b8a4966c93a073d3df1c9f616469bc5aed501d89116ea697302467d07f7 0xc14a0852be93… ↗
9 2026-09-01 48,579 e6f1e5737591b19d024d4ef6df50aade6759113a766c99e4da6aeb44e383242f 0x8a51d06ebe4c… ↗
8 2026-08-31 42,904 7bb4af55c528d1118388acca26fd220b25908e684580c2bc60e58ed5b0d74dc4 0xe6836ae7ffeb… ↗
7 2026-08-30 36,138 b07c460d4eebe1b9cbeda420600d45b907878b7a42288b7c2ad85221ca2d647b 0x96a03a71b38b… ↗
6 2026-08-29 30,571 f6ff4e101260e592ed051f071e3842fe2ad05b49120e4bcd167e5e75ef1abe9d 0x4084589249c5… ↗
5 2026-08-28 24,823 fc49ee11dc31e56014150bef2492bc62df107f0e6220943c9594a55639a86295 0x525c096d3835… ↗
4 2026-08-27 19,564 1e5b2eb9964aa96f1968008e1e55e4941da5a50a0219c9321e5a8da0897a6bc5 0xf4b83069d30c… ↗
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.