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, 4 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.
Sunday, 4 October 2026
- Frozen at
- 06:02 UTC (2026-10-04T06:02:52.423Z)
- Fingerprint
- 76969341bf263ebbcd13962642264fa2bd1e48a628ca471921b52ded5dd84501
- Previous fingerprint
- 50a3c1f19123235fc4ac240d9201351083fd0f6ce64ed06158b80c4c6618b4e7
- Source Board
- 94d0728c234c6e699ef03548c3f6c7095986b3799b0aa3806c72089fdd26a94f
- Canonical version
- 1
- Tickets
- Prime 3: ticket, priced, lost
Prime 4: ticket, priced, lost - 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-04.json --expect 76969341bf26… --prev prime-2026-10-03.jsonDownload verify_prime.py · Download prime-2026-10-04.json · Download prime-2026-10-03.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.
