Verify a Prime ticket
Locked before kick-off. A SHA-256 fingerprint is published before the matches. After settlement, the frozen ticket is released so the fingerprint can be checked.
Record integrity verifiedSunday, 1 November 2026The released ticket file recomputes to the fingerprint published before kick-off. Checked on this server for this page; run the same check in your own browser below.
- Prime is frozen before kick-off, from that morning’s already-frozen Board.
- A SHA-256 fingerprint of the frozen ticket is published straight away, here and on the Prime page.
- The fingerprint chains to the previous Prime day: changing an old ticket would change every fingerprint after it.
- Prime also records the fingerprint of the Board it came from, so the ticket can be traced to its source.
- After settlement the complete frozen ticket is released as a file, every selection included, win or lose.
- Anyone can recompute the fingerprint from that file and compare it with the one published before the matches.
Sunday, 1 November 2026
- Frozen at
- 07:03 UTC (2026-11-01T07:03:38.869Z)
- Fingerprint
- 0e8454e65886de80621601e1d2397d307744c00d2a55f8f16c093d241892291b
- Previous fingerprint
- af0029ef702e4a969805112eb434217cb8218b8847b575aae2724d1d42e2b524
- Source Board
- 81e1a66cfd6f055f630499e4b42303a0fd3e7834c60c78a989a7c28fc0e5d51b
- Canonical version
- 1
- Tickets
- Prime 3: ticket, priced, won
Prime 4: ticket, priced, won - Frozen ticket file
- released: every ticket on this day has settled
Check it yourself, offline
The fingerprint is sha256(prev_hash + "\n" + canonical_json), where the canonical JSON is the ticket definition (selections, probabilities, prices, the source Board fingerprint) with sorted keys and no whitespace. Results are not in it, so settling a ticket cannot change it. A standalone script with no dependencies does the arithmetic:
python verify_prime.py prime-2026-11-01.json --expect 0e8454e65886… --prev prime-2026-10-31.jsonDownload verify_prime.py · Download prime-2026-11-01.json · Download prime-2026-10-31.json · Fingerprint as JSON
What this does and does not prove
- It proves the selections were fixed before the matches and were not changed afterwards.
- It proves the losing tickets are the same tickets that were frozen, because their fingerprints are in the chain.
- It does not prove the selections were good. That is what the record is for, losing days included.
