The ledger
Calls, levels, results and morning maps are sealed with a hash when they are posted, each hash commits to the one before it, and once a day both chains are anchored outside our own systems. Check it yourself below.
What this proves, and what it doesn’t
- Nothing was changed after it was posted. Each entry’s SHA-256 hash includes the hash before it, so editing any past read would change every hash after it.
- It existed by a given time. Each day’s heads file names the newest hash of each chain and is timestamped with OpenTimestamps, which commits it to a Bitcoin block within a few hours. That bounds the time to hours, not seconds; the sealed times on each row come from our own server.
- It doesn’t show a read was right. The record does that, misses included.
- Morning maps joined on 3 Nov 2026. From that session each map is sealed in the chain with The Open and The Map’s calls. The two real maps posted before then, on 1 and 2 Nov, have no entry, and sealing them afterwards would prove nothing.
- The Open’s session post has no entry of its own. It is a summary, after the close, of calls that are already sealed.
- Reads stay members-only. This page shows hashes and times only, never a read’s text or a call’s side.
Check the chain
Your browser fetches every entry, checks that each one points to the hash before it, recomputes each day’s heads file and checks that the anchored heads are in the chains.
Daily anchors
| Day | The Close | The Open and The Map | Anchor | Files |
|---|---|---|---|---|
| Loading… | ||||
To check a proof without us: download the day’s .txt and .ots and drop both on opentimestamps.org, or run ots verify 2026-10-30.txt.ots.
The Open and The Map
| No. | Sealed (ET) | Entry | Hash | Previous |
|---|---|---|---|---|
| Loading… | ||||
The Close
| No. | Sealed (ET) | Entry | Hash | Previous |
|---|---|---|---|---|
| Loading… | ||||