Provably Fair Gambling Explained
Short answer: Provably fair means the game outcome derives from a committed server seed, your client seed and a nonce - so you can recompute every result after the seed is revealed. It covers in-house games only; esports match results come from the tournament, not the book.
"Provably fair" is the one piece of jargon in crypto gambling that deserves its marketing, provided you know what it covers. It is a verification scheme for computer-generated outcomes - dice rolls, crash multipliers, card shuffles running on the book's own servers. It does not cover the sportsbook, the esports odds or the withdrawal button. Here is how the scheme works and what each piece of it proves.
table of contents
The three ingredients
Every provably fair game builds on a commitment scheme [1]:
- Server seed - a random value the operator generates. Before you bet, the site shows you its hash (SHA-256 of the seed). A hash cannot be reversed, so publishing it commits the operator without revealing the value.
- Client seed - a value you control. You can set or rotate it per session, which is the "your input" part of the fairness equation [3].
- Nonce - a counter that increments per bet, so the same seed pair produces a unique outcome for every round.
When the session ends, the operator reveals the server seed. Now you can check: hash the revealed seed, confirm it matches the commitment published before the session, then recompute each bet's outcome from seed + client seed + nonce [1].
From inputs to a number
The most common formulas:
- HMAC-SHA256: HMAC keyed with the server seed over the string "clientSeed:nonce" (sometimes with a cursor for extra rolls); the first bytes of the digest convert to a float, scaled to the game's outcome range - 10,001 steps of 0.00-100.00 for classic dice [2].
- SHA256-concat: the older crypto-dice scheme - hash the concatenated seeds and nonce, read the first 32 bits as an integer, scale to the outcome range.
- SHA512-chunk schemes - some sites read hex chunks from SHA-512 digests, skipping oversized chunks, modulo the outcome range.
The details matter: the scaling scheme, the number of steps, the modulo. A verifier that assumes the wrong formula produces different numbers from a correct game - a mismatch is not automatically proof of rigging. It is a prompt to check the scheme, the nonce range and whether the seed rotated mid-session.
What a match proves
A successful verification proves the displayed outcome followed mathematically from the inputs, and - with the commitment check - that the server seed was fixed before your session started. Nobody can have cherry-picked outcomes after seeing your bets.
What it does not prove: that the operator runs this code in production rather than a staged version; that every game on the site uses the same scheme; that the odds feeding the sportsbook are honest; or that the operator pays withdrawals. Fairness of the RNG is one brick in the house. The trust facts (license, operator, red flags) are the other walls.
Where it matters for esports bettors
If you are on this site for esports markets, provably fair is peripheral - your prices are market prices. It becomes relevant when the same book runs casino-style originals, which most crypto books do. If you clear a bonus on in-house games, or play a duel between maps, that is where the seeds matter.
How to verify, practically
- Before betting, find the fairness page and note the scheme and the published seed hash.
- Set a client seed you chose - not the default.
- After the session, take the revealed server seed and run several nonces through our verifier. It checks the commitment and recomputes outcomes locally; nothing leaves your browser.
- Compare with the site's own results. A mismatch means wrong scheme, wrong nonce range, or a mid-session seed rotation - the operator's fairness page explains rotations.
The one-line takeaway
Provably fair is reproducible math, not a guarantee - it verifies the machine, not the house. Use it to rule out rigged in-house games; use the reviews and dated sources for everything else.
The scheme names are standardized but the outcome mappings are not: two sites can both say HMAC dice and scale the digest differently, which is why the verifier asks for the exact range. If an operator refuses to reveal the server seed for a completed session, treat that as a fairness failure regardless of what the marketing page claims. Rotation policies differ: some books rotate seeds per session, others per bet. Both are fine as long as the commitment was published before the first roll of the session.
FAQ
Does provably fair apply to sports and esports odds?
No. Match outcomes come from the tournament, and prices come from the book's odds model - neither is seed-based. Provably fair covers in-house games (dice, crash, mines) on the same site.
What is the commitment for?
The server seed hash published before your session proves the seed was fixed in advance - without it, the operator could switch seeds after seeing your bets. With it, every roll is reproducible from inputs you control or can check.
How do I verify a roll myself?
Take the revealed server seed, your client seed and the nonce, run them through the documented formula (HMAC-SHA256 or SHA256-concat), and compare the result with what the game displayed. Our verifier does the math locally.
Is provably fair a sign the book is safe?
It is one brick, not the house. Fair game logic says nothing about whether the operator pays withdrawals, keeps licenses current or stays solvent. Read the red flags section of every review alongside the fairness facts.
Ready to pick a book? The comparison table has the live values, the finder narrows them down:
Sources
- Wikipedia - Commitment scheme - accessed 2026-09-24
- Wikipedia - HMAC - accessed 2026-09-24
- Bitcoin design guide - randomness basics - accessed 2026-09-24