Certificate of Pick Authentication #416 · 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: Undercover Affair
Race: Nottingham · 2 July 2026 · 15:00
Product: Top Rated Today (Sly Man) · Top Rated — Top Consensus
Advised odds: 15/8
Confidence: Speculative (raw 2)
Prompt version: top_rated_v1_2026-07-08
Predicted at: 2026-07-08T22:13:45.957944+01:00

Cryptographic Seal

Leaf hash: e40870d2fda8bf9db8e00ad48fbe0bef79abd592fd74cc9f0a41ed8e443a6ddf
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":"consensus","race":{"course":"Nottingham","external_id":"rac_11995906","internal_id":2363,"race_date":"2026-07-02","race_time":"15:00"},"schema":"sr-pick-v1","selection":{"advised_odds":"15/8","confidence_final":"Speculative","confidence_raw":"2","horse":"Undercover Affair","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	e3e9a9be2aa7c58094bc35be0715cbaccec2e5160f949142cff975f95c6d352c
2	right	b4ce460ad476764a88bb8f5fbf7f0002f68aaac8f2ad241e908f07b193c8a3ec
3	left	9d2b554c7db08822bc263ca1c10c21760d493c596e4c13b6c47755d5a5055ae2
4	left	1f7fe33bf239035e6e8536cd8b60b20a72b35207b42dfc4ffb167eedcc798fd8
5	left	c3c4ffb271c68a9d689182917ef3942747a6040af5ce1ca8abe1fc90165e5dd4
6	left	b495d7542cc68c4b7514051aff9c40ee645b401fdf6a48deafd015554c949f6a
7	left	18098d0ad2005f6c8a767a2aceec92cb16c50e0350a0aeb358818e8c739d9967
8	right	f384b0629d9042022b8062f38497000b02dafa843e81b7fba3c37144f3b49f92
9	right	559310ef76957df08e5f62efc49ff6649a36113b72a52a9a4471bd1801615514
10	left	f294ff8c83ee2bf537f6f3a850e09ef12f44b3915f1df793eb9ebfc3a7648f55

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