Certificate of Pick Authentication #196 · 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: Another Abbot
Race: Salisbury · 30 June 2026 · 15:37
Product: Horses to Watch (Sly Man)
Advised odds: 9/4
Confidence: Medium
Prompt version: htw_backfill_v1
Predicted at: 2026-07-07T09:56:15.528689+01:00

Cryptographic Seal

Leaf hash: 61d54531578a7676b1e79389c79ca6816e75d20835cfaade72420dc35e281182
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":"htw_backfill_v1"},"committed_at":"2026-07-13T21:10:28Z","issuer":"saturday-racing.com","predicted_at":"2026-07-07T08:56:15Z","product":"horses_to_watch","product_lane":"","race":{"course":"Salisbury","external_id":"rac_12006436","internal_id":2273,"race_date":"2026-06-30","race_time":"15:37"},"schema":"sr-pick-v1","selection":{"advised_odds":"9/4","confidence_final":"Medium","confidence_raw":"","horse":"Another Abbot","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	6280004332979cff2763881e9d323fed5b081fe8f1508e4f521376afa722f8af
2	right	0ed8d6bdde6223293033268fe5f16fef18a7ec2f4e1786d4e7a9eba8e705fb25
3	right	71c027f6acac7e3c537002aa16177d5bc24ca4164172c3e8bc14722f59091bc1
4	left	850a305a46d1ab56649dfdd2fb90d857a14414ad9958ae3caee6a209c012f1e5
5	left	e03f92d958e5413163b35715e1d7369afc39ca8e31ac016bd7de801fade5670d
6	right	0a5bb34874ff669c5cf989b9de5608e66f456e8a2c0e4549102b83804e867c02
7	right	2cc9e7f1f0b7c3ec0e9bb3fdcf68995f9a6e05667eb83c69c735851531edb0da
8	right	f1c99ba68a2d45d1bb79f40edc8b534afd41f7a23fe00327643be3c20b514374
9	left	c1144f953d5061b1e3ec979350290e5e7106de524b96bf728133a9efff0efd59
10	right	e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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