Certificate of Pick Authentication #406 · Saturday Racing

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: Nabati
Race: Yarmouth · 2 July 2026 · 15:09
Product: Top Rated Today (Sly Man) · Top Rated — Top Signals
Advised odds: 1/6
Confidence: Speculative
Prompt version: top_rated_v1_2026-07-08
Predicted at: 2026-07-08T22:13:45.893147+01:00

Cryptographic Seal

Leaf hash: 9e64d4b9ddbb58d24a5e1b458229682ffbcd7b5213353db9f99c7dbc9b1caeb6
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.

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":"story_score","prompt_version":"top_rated_v1_2026-07-08"},"committed_at":"2026-07-13T21:10:28Z","issuer":"saturday-racing.com","predicted_at":"2026-07-08T21:13:45Z","product":"top_rated","product_lane":"signals","race":{"course":"Yarmouth","external_id":"rac_11988730","internal_id":2375,"race_date":"2026-07-02","race_time":"15:09"},"schema":"sr-pick-v1","selection":{"advised_odds":"1/6","confidence_final":"Speculative","confidence_raw":"","horse":"Nabati","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.

#	Position	Sibling hash
1	right	9e7fefbb8dd9863a631743ff928710e5ba0d61c1fb91334a1b872f1f1ac2145f
2	right	60c61ff6ca410356c41535252ea2f621fdd5cf5915ea9d198581f7a1cc490e1c
3	left	d76524049cab9b6144a0db3090c81f7d680043d7a8ee3613af2a7b76dcc57d78
4	left	29b9329678105f7b94799666df64bff979212f7378d609f460469c33636d7925
5	right	32969f22a66e840a786dccb6b5ee6e302709d53b2206fb9aebccabc2478b63f7
6	right	122ad8c3830c8717ffb38cb520c4f4916841ee7438458e522353d27690ee23f0
7	left	8ecad2493bca745bc0527c62a707de924168e44ffe66dc178ff870ba82aa045e
8	left	9a677d21c2cd9160c97a508996b4307c85b3aa9b95597b3eca8c62f864ebab76
9	left	c1144f953d5061b1e3ec979350290e5e7106de524b96bf728133a9efff0efd59
10	right	e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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