Certificate of Pick Authentication #404 · 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: Speechman
Race: Beverley · 3 July 2026 · 18:00
Product: Top Rated Today (Sly Man) · Top Rated — Top Market Movers
Advised odds: 11/1
Confidence: High (raw 61)
Prompt version: top_rated_v1_2026-07-08
Predicted at: 2026-07-08T22:13:45.877059+01:00

Cryptographic Seal

Leaf hash: b523513cf0cd2bef0c001f18af8a9f9d7e849cbfc0746b21920532ced17142eb
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:27Z","issuer":"saturday-racing.com","predicted_at":"2026-07-08T21:13:45Z","product":"top_rated","product_lane":"movers","race":{"course":"Beverley","external_id":"rac_11989172","internal_id":2395,"race_date":"2026-07-03","race_time":"18:00"},"schema":"sr-pick-v1","selection":{"advised_odds":"11/1","confidence_final":"High","confidence_raw":"61","horse":"Speechman","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	left	b4f92a26176c527a471aaa57b452809b71234ba052455a78269d7cf8cadba15a
2	right	86dc93444ced3476e4cefc0df262c9972132e530d829a757471c2b970c164d75
3	left	9f94e6607270bea03cb4c00dba02beba3a8ac480a21a04363bf3e8872f78955c
4	right	f8c4bc101105bfaa39b7c59eacdd5fb08c4c3413ac394497650689391b07de2d
5	right	cdc43ee135d27ed2e4e2e9c87e3d3d2a18ea09ac1b149404ecdd52998e761386
6	right	204feec8495b2d1b806e60958c15c429141021ee238922bdfcbd4c87367079be
7	right	7b966ba7fb6479ee18f2a8f9b8925b3c3366b9fe81cdbeb08938a02c83890686
8	right	f384b0629d9042022b8062f38497000b02dafa843e81b7fba3c37144f3b49f92
9	right	559310ef76957df08e5f62efc49ff6649a36113b72a52a9a4471bd1801615514
10	left	f294ff8c83ee2bf537f6f3a850e09ef12f44b3915f1df793eb9ebfc3a7648f55

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