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
Yquem
Race
Leopardstown · 9 July 2026 · 19:38
Product
Pick Winner (Mr Fox)
Advised odds
4/1
Confidence
Medium
Prompt version
v3_b557cbd4
Predicted at
2026-07-08T19:03:19.312555+01:00

Cryptographic Seal

Leaf hash
2fc329258618a062bd31a4fb63ce869905884c5e16db5a5380eb00a0b4959f05
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:27 BST

Certificate reference

#302

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:27Z","issuer":"saturday-racing.com","predicted_at":"2026-07-08T18:03:19Z","product":"pick_winner","product_lane":"","race":{"course":"Leopardstown","external_id":"rac_12016277","internal_id":2648,"race_date":"2026-07-09","race_time":"19:38"},"schema":"sr-pick-v1","selection":{"advised_odds":"4/1","confidence_final":"Medium","confidence_raw":"Medium","horse":"Yquem","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 302f0f1e4665e46ad179e3d251d8d33e55e3e1be496af67cb8304e6ab909858e
2 left 4bbc61e6fb976598bf6e907cba3e158399461ec93c2a034200127f32a8195cdb
3 left dc9d48029ae6e1ffc15ca8717ebb8b1b02ef4c7a1876605f34434666febb83b0
4 left d990640555a8943eca540a46bbd6c8e52b86848d052bd147ffd5c77f785556c8
5 right 3e0f8231daebd0e796cd717336eb322ee18dc97f3c190073f937036a0fef207f
6 right 7b82e1439f3e2ced375831c6c20f3fbb9f5a25088a3ad284db7ae38222b4fb9a
7 right 5f0f7abcd778c76063fcb7f47d37dd69ca800d95c3310c502cc42ed16873af2c
8 left 258ce92dcccd21d1d3bbbb39ac789ad1349e3db2aadbe660b7ed0a8637d8148f
9 right a37bae6f6b56af99833b4e131855bb087cd4e3a90918a4dfd59d83ac87f8f303
10 right e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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