Each line below is a hash covering a million rounds, published before the first of them was played. Hash the key from any finished round, hash it forward to the start of its segment, and you land on the number in that row — or you catch us. There is no third outcome.
These are read from the chain files themselves, every time this page loads, by the same code the game uses. Nothing here is typed in by hand: a fairness page carrying a number nobody can check against the thing it describes is the fault it exists to prevent.
| Rounds | Links | Commitment | Published |
|---|---|---|---|
| 1–100,001 | 100,001 | c3dac9aa7281025402c39c1d7de383425f16dd817cad1780b96aeffd55cf6ee1 | not yet No operator should be running live rounds against this segment until it is published. |
| 100,001–1,100,001 | 1,000,001 | c1c06639a5c460864ef4091304c306fa2667392cd63d85b68896ee3055883052 |
2026-08-21
where |
| Rounds | Links | Commitment | Published |
|---|---|---|---|
| 1–1,000,001 | 1,000,001 | — |
2026-08-21
where Recorded after its rounds had already begun. A commitment published afterwards proves nothing — it is shown here rather than hidden, because the record being honest is the only thing that makes the rest of it worth reading. |
The same figures answer as JSON, without a login, so you can compare this page against the endpoint rather than taking either on trust:
/lab/?what=commitments · the method in full
If the two ever disagree, the disagreement is the story. Tell us and we will publish what happened.
Each segment covers a fixed number of rounds. The next one must be published before its first round runs, which means the deadline is a round number, not a date in a calendar — and the rounds keep coming whether or not anybody is watching the clock.