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 verifiedWednesday, 2 September 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.
Wednesday, 2 September 2026 Launch validation
- Frozen at
- 18:14 UTC (2026-09-02T18:14:08.509Z)
- Fingerprint
- d78027fd25b0ea2c9a11fcf77216b5f49ccf76e41b75b137229d9b98246a7cf6
- Previous fingerprint
- genesis
- Source Board
- 735bed586161c1c4eaef6376c3c091df65132ab3785aab6674e8202d3c166a0d
- Canonical version
- 1
- Tickets
- Prime 3: ticket, priced, won
Prime 4: no ticket (Prime 3 is available. Prime 4 isn't: only three different qualifying Board fixtures were published.) - 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-09-02.json --expect d78027fd25b0…Download verify_prime.py · Download prime-2026-09-02.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.
