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 verifiedMonday, 26 October 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.
Monday, 26 October 2026
- Frozen at
- 07:02 UTC (2026-10-26T07:02:32.293Z)
- Fingerprint
- 83458ff0331d10ddfc31220be3bd0ffb2609c589bdd8200e805156a89a58fe3c
- Previous fingerprint
- 62082132877252e4e0e596edc091ef897ae805baea58c645013e103049e27d8c
- Source Board
- 8f1e20675c33683ba71d315893eb4adeb88d8faff9f9fcccd9cca95fae2121ba
- 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-10-26.json --expect 83458ff0331d… --prev prime-2026-10-25.jsonDownload verify_prime.py · Download prime-2026-10-26.json · Download prime-2026-10-25.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.
