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, 16 October 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, 16 October 2026

Frozen at
06:03 UTC (2026-10-16T06:03:21.813Z)
Fingerprint
36c3cd5f47a93f07af9f62c70301a6f3517b84f245881194bf3469b426618804
Previous fingerprint
115d3e73023d72b1ed64a5397f8b11c30650f63b4c77144813edfe23f8e69623
Source Board
d597d1584bae732889336f189abb1cab80c35745d2387bbde9297e81b388e3f3
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-10-15

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-16.json --expect 36c3cd5f47a9… --prev prime-2026-10-15.json
Download verify_prime.py · Download prime-2026-10-15.json · Fingerprint as JSON

What this does and does not prove