Our public record, frozen.
Once a month Prolepsia saves every question on its public page into one file: its wording, its resolution rules, every forecast published on it, the latest report with its sources, and the outcome where there is one. The file's SHA-256 hash is posted on X, and the file is stamped in the Bitcoin blockchain with OpenTimestamps.
The forecasts are public already, so the hash hides nothing. It fixes the record in place. If a forecast, a question or its wording changed after a snapshot, the file would no longer match what this site shows.
Every snapshot
- Taken
- 6 November 2026, 12:31 UTC
- File
- prolepsia-public-record-20261106T123102Z.json (1.7 MB)
- SHA-256
5ad01f7148356de960558a6a0b4aabea1a52f015561fa131d9019eed60fb58c7- Bitcoin proof
- Download the proof
- Previous snapshot
- None. This is the first snapshot.
How to check a snapshot
Download the file and run one command. The result must match the hash above exactly. Use the downloaded file: a copy pasted from a web page can differ by one space and fail the check.
macOS
shasum -a 256 prolepsia-public-record-20261106T123102Z.jsonLinux
sha256sum prolepsia-public-record-20261106T123102Z.jsonWindows (PowerShell)
Get-FileHash -Algorithm SHA256 .\prolepsia-public-record-20261106T123102Z.jsonTo check the date, drop the file and its proof file on opentimestamps.org.
To check that the record has not changed since, compare any question on this site with its entry in the file. Every forecast up to the snapshot's date must be the same.
Why each snapshot names the one before
Each file holds the hash of the snapshot before it, so the snapshots form a chain. A question or a forecast removed from the record would show as a gap between two of them.
A forecast published after a snapshot is frozen by the next one, up to a month later.