Certificate of Pick Authentication #313 · 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: Lushill
Race: Chepstow · 8 July 2026 · 18:26
Product: Top Rated Today (Sly Man) · Top Rated — Top Signals
Advised odds: 11/4
Confidence: Speculative
Prompt version: top_rated_v1_2026-07-08
Predicted at: 2026-07-08T22:13:45.190023+01:00

Cryptographic Seal

Leaf hash: cff135c3db443f145763f1422b242d8c82cc31e209e767c882c49aee2f1b3812
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":"signals","race":{"course":"Chepstow","external_id":"rac_11990251","internal_id":2584,"race_date":"2026-07-08","race_time":"18:26"},"schema":"sr-pick-v1","selection":{"advised_odds":"11/4","confidence_final":"Speculative","confidence_raw":"","horse":"Lushill","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	cfb76dc9a82651cb0435a45c42a8549f55e9abbc728bf6ecbda6495ee832bbaa
2	left	3a9d6aaf80b82ae447f309c7d0eca3e00a9f811cd136fd0f398d149186c43962
3	left	1172f0eef7256fd57da4181dd4f384cd8e067dfb0e47d0d36dfab3042246f810
4	right	0ca86935adce425322f530f3b80609aa45ed4f8ee698770a136b9a652fb53870
5	right	ecdaa6e2e1784cbd4741db232c48ecd4cd3ea1ee82d986ebbe991c6a27a0b043
6	right	8d365ed1fcd50ce4692074b8d288bcbca840a0024697303b2be824fc4a5251f3
7	left	18098d0ad2005f6c8a767a2aceec92cb16c50e0350a0aeb358818e8c739d9967
8	right	f384b0629d9042022b8062f38497000b02dafa843e81b7fba3c37144f3b49f92
9	right	559310ef76957df08e5f62efc49ff6649a36113b72a52a9a4471bd1801615514
10	left	f294ff8c83ee2bf537f6f3a850e09ef12f44b3915f1df793eb9ebfc3a7648f55

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