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
Furturra
Race
York · 11 July 2026 · 14:02
Product
Bet of the Day (Sly Man)
Advised odds
5/1
Confidence
MEDIUM (raw 7.29)
Prompt version
v1_f12e6534
Predicted at
2026-07-11T07:58:25.692715+01:00

Cryptographic Seal

Leaf hash
0dbc355faafff50949ac2c1ad9b9952b8bf4b7e718555f02906a0731453f03bb
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

#587

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":"bod_composite","prompt_version":"v1_f12e6534"},"committed_at":"2026-07-13T21:10:26Z","issuer":"saturday-racing.com","predicted_at":"2026-07-11T06:58:25Z","product":"bod","product_lane":"","race":{"course":"York","external_id":"rac_11991421","internal_id":2736,"race_date":"2026-07-11","race_time":"14:02"},"schema":"sr-pick-v1","selection":{"advised_odds":"5/1","confidence_final":"MEDIUM","confidence_raw":"7.29","horse":"Furturra","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 0dee2edc77201bfaf2ac9f5dedc5220607cb8f91f22a8073ff24ffa7874ad2ba
2 left 2a27cf061140eb611d31cfcc6864a0814a945c4b10d8bebfa5de764b73ecaa0d
3 right 50f500b7efcbdfdd6ae74911225d22327c31cdc6489c047f5a0019a1affb17f0
4 left d4f6a28ec34138491ba205618277d376c1dd4b6c37514fd343a3379de704896a
5 right 8f4a0fd246d462fe2734244e69f67fde160b71cf86c07701b68e4e2ede4983a5
6 left 28a79af419252db0d5355ceb206307eccea1dfa0bc74e1b70403c4125df54885
7 right a1446b8f053c3881b7e667ad2875514c1369218939a0da4c16d065175c0bd80d
8 right 7f26ee208367c64ad8017566de1de4e6ffc26d447963c5f0ab2e3225cec0656b
9 right a37bae6f6b56af99833b4e131855bb087cd4e3a90918a4dfd59d83ac87f8f303
10 right e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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