/ VERIFY

Public hash-chain verifier

Every NuroPicks pick is committed with a SHA-256 hash before the game starts (the pre-commit hash) and a second SHA-256 over the captured closing line after the line moves (the closing hash). Both hashes are stored UNIQUE in the picks table, and the immutability trigger blocks every UPDATE after insert. Paste any hash you have - even a prefix of 8 characters from a Discord embed footer - and we will resolve it back to the canonical /record entry. If the hash matches, the pick was not edited after publication. If the hash does not resolve, either the row never existed or you are looking at a forgery.

Match: pre-commit hash

2-Leg Parlay (2 legs) +148

Cross-Sport (MLB + WNBA) · MLB+WNBA · 2 legs · parlay · +148 · 1u · result: LOSS

pre-commit (pick_hash)a36c5eb82096c97c63559595852dcec4385233329d9470f088efe0152882bc1c

closing-line (closing_hash)20c1056738156e0cd9ad4857794833b2a9ed29ed3ae01eb0b8e6b2360d73c5c9

View full /record entry Browse all picks

How verification works

When a pick is locked, our publisher computes SHA-256(pick_uuid || odds || market || posted_at || nonce) and stores it in picks.pick_hash with a UNIQUE constraint.
The first 12 hex chars of the pre-commit hash are surfaced in the Discord embed footer the moment the pick is published.
When the closing line is captured (typically 5 minutes before tip), we compute SHA-256(pick_uuid || closing_odds || closing_at) and store it in picks.closing_hash, also UNIQUE.
Both columns are append-only - the immutability trigger from migration 0017 raises an exception on any UPDATE to a settled row.
This page does the inverse: paste any hash and we resolve it back to the canonical row. The hash either matches (proof) or does not (forgery / never existed).