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.

Commitment publishedFriday, 6 November 2026Frozen before kick-off. The full ticket is released after every ticket on this day has settled.
  1. Prime is frozen before kick-off, from that morning’s already-frozen Board.
  2. A SHA-256 fingerprint of the frozen ticket is published straight away, here and on the Prime page.
  3. The fingerprint chains to the previous Prime day: changing an old ticket would change every fingerprint after it.
  4. Prime also records the fingerprint of the Board it came from, so the ticket can be traced to its source.
  5. After settlement the complete frozen ticket is released as a file, every selection included, win or lose.
  6. Anyone can recompute the fingerprint from that file and compare it with the one published before the matches.

Friday, 6 November 2026

Frozen at
07:03 UTC (2026-11-06T07:03:05.134Z)
Fingerprint
f35bbedc943db0d6771f60a7aa644090e3cba73022261a967b0bd01ad597c628
Previous fingerprint
cab98b350b14920a951378168ef7d77f261295ba8fb299c53cc2af7538456a3a
Source Board
5a7f0eeeff54e47546ebd77744abae85c892f9bfb404e0a5c94933d8ecc483d9
Canonical version
1
Tickets
Prime 3: ticket, priced, pending
Prime 4: ticket, priced, pending
Frozen ticket file
released after every ticket on this day has settled

← 2026-11-05

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-06.json --expect f35bbedc943d… --prev prime-2026-11-05.json
Download verify_prime.py · Download prime-2026-11-05.json · Fingerprint as JSON

What this does and does not prove