Certificate of Pick Authentication #449 · 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: Black Storm
Race: Carlisle · 9 July 2026 · 16:55
Product: Top Rated Today (Sly Man) · Top Rated — Top Market Movers
Advised odds: 9/4
Confidence: High (raw 53)
Prompt version: top_rated_v1_2026-07-08
Predicted at: 2026-07-09T08:02:17.794030+01:00

Cryptographic Seal

Leaf hash: 260f16306cabf214b5d12cd49981b3c7aee06de7a7793f6af27e0c7874287209
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-09T07:02:17Z","product":"top_rated","product_lane":"movers","race":{"course":"Carlisle","external_id":"rac_11990446","internal_id":2615,"race_date":"2026-07-09","race_time":"16:55"},"schema":"sr-pick-v1","selection":{"advised_odds":"9/4","confidence_final":"High","confidence_raw":"53","horse":"Black Storm","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	263e626d8b87cbda383ab7cd82269b9df36b1b3492dae07de05a36b2b2d56872
2	left	00f04817d9001e6c23692445d95d7e20b8eb3f786643d548614e332973eb86dc
3	right	6caf1b2cdbad5d376102d2a74c20f43bbd9c7d7772563808cc95e44f60d9b99d
4	right	cec8ae408b34325b8433aee0744f178d4729920855a19ad661996f664ae1d63e
5	left	671e30e2e0c413e9f6557469a276abe44c7c6c9df2103b24b8dbf131cfd03238
6	left	d2f5951c321258f1da44d8e3609710b4c9c90fac4d41e3ca7536c70ae340789e
7	left	0af567e55c1ca3698f0d247913af3961bd1e207eb3c7b8dd318659719ff7e32e
8	right	7f26ee208367c64ad8017566de1de4e6ffc26d447963c5f0ab2e3225cec0656b
9	right	a37bae6f6b56af99833b4e131855bb087cd4e3a90918a4dfd59d83ac87f8f303
10	right	e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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