Saturday Racing · The Transparency Ledger

Certificate of Pick Authentication

Issued under schema SR-PICK-V1

Verifying in your browser…
Hashing the pick's canonical bytes with your device's SHA-256.

This is to certify that the pick recorded below was cryptographically committed to Saturday Racing's transparency ledger before the race ran. The commitment is a SHA-256 leaf hash of the canonical bytes; any subsequent tampering breaks the hash and this certificate turns red. The check runs on the reader's own device — no trust required from us.

The Pick

Horse
Two Tribes
Race
Newmarket · 11 July 2026 · 15:25
Product
Pick Winner (Mr Fox)
Advised odds
17/2
Confidence
Medium
Prompt version
v3_b557cbd4
Predicted at
2026-07-11T07:45:55.612622+01:00

Cryptographic Seal

Leaf hash
62859d5d01b37a635c8a410aed00ed17a79f9ebfa30d0a7c54b706eded29f08d
Your browser
Batch
13 July 2026 · 709 leafleaves · inspect batch →
Merkle root
eba1d4cb07b18df5f26ea6211dae664c2a8d9ce7bdcd95a3a7d9da03ed6cf62b
Your browser walk
On-chain
Off-chain verified. Anchoring on-chain is a separate, gas-gated step.

Signed

Saturday Racing Editorial Ledger

Committed 13 July 2026 at 22:10:26 BST

Certificate reference

#546

Technical appendix — canonical bytes & Merkle proof

The canonical bytes

This is the exact JSON that was hashed. Copy it, run sha256sum on it yourself, and you should get the leaf hash above.

{"attribution":{"pick_source":"llm","prompt_version":"v3_b557cbd4"},"committed_at":"2026-07-13T21:10:26Z","issuer":"saturday-racing.com","predicted_at":"2026-07-11T06:45:55Z","product":"pick_winner","product_lane":"","race":{"course":"Newmarket","external_id":"rac_11963224","internal_id":2725,"race_date":"2026-07-11","race_time":"15:25"},"schema":"sr-pick-v1","selection":{"advised_odds":"17/2","confidence_final":"Medium","confidence_raw":"Medium","horse":"Two Tribes","position_claim":"win"}}

The Merkle proof

Each hop is a sibling hash. Your browser walks these from the leaf up to the root, hashing pairs at each step.

#PositionSibling hash
1 right 63f5e61c6d4e096cf09432e257938cce9396ac22704274f8ed97eeb148333bce
2 left db8faee48eb46335a51450760426e230bb1d26066da4ed1406b7c4949a01e003
3 right 71c027f6acac7e3c537002aa16177d5bc24ca4164172c3e8bc14722f59091bc1
4 left 850a305a46d1ab56649dfdd2fb90d857a14414ad9958ae3caee6a209c012f1e5
5 left e03f92d958e5413163b35715e1d7369afc39ca8e31ac016bd7de801fade5670d
6 right 0a5bb34874ff669c5cf989b9de5608e66f456e8a2c0e4549102b83804e867c02
7 right 2cc9e7f1f0b7c3ec0e9bb3fdcf68995f9a6e05667eb83c69c735851531edb0da
8 right f1c99ba68a2d45d1bb79f40edc8b534afd41f7a23fe00327643be3c20b514374
9 left c1144f953d5061b1e3ec979350290e5e7106de524b96bf728133a9efff0efd59
10 right e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

Server-reported status: off_chain_verified · Ledger overview at /verify/