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
More Thunder
Race
Ascot · 11 July 2026 · 14:27
Product
Pick Winner (Mr Fox)
Advised odds
11/10
Confidence
Medium
Prompt version
v3_b557cbd4
Predicted at
2026-07-11T07:43:53.977226+01:00

Cryptographic Seal

Leaf hash
591a3460950f4eeb357e059ea57bae442d782c8a2c355a5dfba74cf6492bcbb0
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

#538

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:43:53Z","product":"pick_winner","product_lane":"","race":{"course":"Ascot","external_id":"rac_11991005","internal_id":2701,"race_date":"2026-07-11","race_time":"14:27"},"schema":"sr-pick-v1","selection":{"advised_odds":"11/10","confidence_final":"Medium","confidence_raw":"Medium","horse":"More Thunder","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 5920e812c6e249ea77949f723eef8dedb77d876f3acf37d137fa993a8a170e72
2 right 0b740efb2739ea8c35ff3e64325f0158392960bc8b4ce4cd87a9316f8dc4ee8f
3 right 26178c23d24a7d1ddaed1bdf8a8cc2797241726693996b26faeb34d11aa227e1
4 left de42128ab75b05c1180b53296e109b29d46a6c35f5c4a2161f5ae3eaa7ed546c
5 left 9c35144997c1f95839a65dfc94dc3a1139864f7417424a4c114d696b14c74df8
6 left fc52f76fefc833e1107b03796f834d4ba1336aeb1778053c068d9688bda96b1d
7 left abd1f2af8516869713aed81c9f26f27b73cfb533f542009e428008b662810a09
8 left 258ce92dcccd21d1d3bbbb39ac789ad1349e3db2aadbe660b7ed0a8637d8148f
9 right a37bae6f6b56af99833b4e131855bb087cd4e3a90918a4dfd59d83ac87f8f303
10 right e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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