Pick verification
How to verify sports betting picks before trusting a record.
Screenshots and social posts are easy to edit. A verifiable pick record preserves what was selected, the available price, and independent proof that the record existed before the event.
Why a timestamp alone is not enough
A timestamp has value only when it is bound to the exact contents of a pick. If the selection, line, or odds can be changed without changing the timestamp proof, the record is not independently auditable. Verification therefore starts by converting the complete publication into a stable canonical representation and hashing those exact bytes. The receipt should include event identity, scheduled start, selection, market, line, stake, price, bookmaker, quote identity, provider-response timing, and model provenance. Omitting the price or event identity can leave enough ambiguity to substitute a more favorable interpretation later.
What a cryptographic receipt proves
A SHA-256 receipt hash is a compact fingerprint of canonical pick data. Change even one character in the canonical payload and the resulting hash changes. A public verification page can recalculate the hash and show whether the displayed record still matches the original receipt. A hash by itself does not prove when the data existed. It must be submitted to an independent timestamp authority before the event begins. A valid RFC 3161 timestamp token binds the hash to a trusted signing time. Using more than one independent authority reduces reliance on a single service.
Verify the source price as well as the publication
A bettor cannot evaluate a pick without the price that made it actionable. Strong source evidence names the bookmaker and quote, records when the provider response arrived, and hashes the exact response bytes before parsing. That makes it harder to swap in a better price after the market moves. Raw response retention may be restricted by provider terms. When the underlying bytes cannot be retained, the record should say so rather than claim content-addressed storage that does not exist. A response hash still detects whether retained bytes match, but it cannot recreate unavailable source data.
Settlement must be append-only
The original publication should never be overwritten with the final result. Settlement belongs in a later event that references the receipt, records when grading occurred, and has its own integrity hash. Corrections should be new events too, preserving both the earlier state and the reason for the correction. This event model creates a readable lifecycle: publication, timestamp proofs, closing-line capture, settlement, and any correction. Public performance can then be reconstructed from the original receipt and valid events instead of trusting editable convenience columns.
How to inspect a verification page
Begin with the scheduled start and publication time. Confirm the publication came first. Next compare the selection, market, line, price, and bookmaker with the canonical payload. Recalculate or rely on an open verifier to recalculate the receipt hash, then inspect each timestamp authority result and signing time. Finally, review lifecycle events. A valid settlement event should explain the result and unit profit without modifying the pick. Missing evidence should remain visibly unavailable. A verification system becomes less trustworthy when every record looks perfect; honest systems preserve failures and limitations. Canonical payload parses and hashes correctly. Publication precedes the scheduled event start. Named-book quote and provider-response evidence are present. Independent timestamp proofs match the receipt hash. Settlement and correction events validate independently. Legacy records are clearly separated from the current standard.
What verification cannot prove
Cryptographic verification cannot prove that a model is profitable, that the quoted price was available to every bettor, or that future picks will win. It proves a narrower but important fact: the preserved record has not been silently rewritten and credible timing evidence places it before the event. That foundation makes performance analysis more meaningful. Winnor's public ledger intentionally keeps prior-standard history visible with limitations while applying the stronger receipt standard prospectively to new official picks.