Saturday Racing · The Transparency Ledger

Certificate of Pick Authentication

Issued under schema SR-PICK-V1

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
Bloom
Race
Cork · 14 June 2026 · 16:48
Product
Horses to Watch (Sly Man)
Advised odds
10/1
Confidence
Medium
Prompt version
htw_backfill_v1
Predicted at
2026-07-07T09:56:14.565237+01:00

Cryptographic Seal

Leaf hash
050cebcc74f7ec5481642999cde46b1864df196b9554d27a5261d271aff95170
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.

Signed

Saturday Racing Editorial Ledger

Committed 13 July 2026 at 22:10:28 BST

Certificate reference

#118

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:14Z","product":"horses_to_watch","product_lane":"","race":{"course":"Cork","external_id":"rac_11980358","internal_id":1659,"race_date":"2026-06-14","race_time":"16:48"},"schema":"sr-pick-v1","selection":{"advised_odds":"10/1","confidence_final":"Medium","confidence_raw":"","horse":"Bloom","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.

#PositionSibling hash
1 left 04c7ebd1effdc749159dec84c9cfe8142be97b4e30015235cf473c82334a6b3d
2 left 19162c074f13feabda730aaaa68a538cd8bc2734d7a694b7cafa0d7419652a3c
3 right ca408dfd8d04e7c28bfb30c91c55894c606439003f5dd96a42a470124ba75aa1
4 left 296e58954fc87676d3b6c16a18ab9bdd46df991cdffae9426d4135a59f03b085
5 right ca53ef3fd171e0565048e3b7ef22209c70a4ebf16fd56a95c0461d55050a3323
6 right 176dfb74ea168aed799314f1c1366361f5a82fdfca5ef82a72a3c3a04d0a9176
7 right a1446b8f053c3881b7e667ad2875514c1369218939a0da4c16d065175c0bd80d
8 right 7f26ee208367c64ad8017566de1de4e6ffc26d447963c5f0ab2e3225cec0656b
9 right a37bae6f6b56af99833b4e131855bb087cd4e3a90918a4dfd59d83ac87f8f303
10 right e25c8d2b935f54f140bee5f6c7b02a176294b2ed6153543d94a92504abeba294

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