Provably fair is a cryptographic commitment scheme: the casino locks in its randomness before you bet, you contribute randomness of your own, and after the fact you can recompute every result and confirm nothing was manipulated. It applies to crypto casinos' in-house games — crash, dice, plinko, mines and the rest of the originals family — and it is the one genuinely new fairness idea online gambling has produced.
The three ingredients
| Component | Who provides it | What it does |
|---|---|---|
| Server seed | Casino — committed as a hash before play | The casino's randomness, locked in advance |
| Client seed | You — visible and editable in the game settings | Your randomness; prevents precomputation |
| Nonce | Counter — increments each bet | Makes every bet under one seed pair unique |
Each result derives from a deterministic function of all three: result = f(serverSeed, clientSeed, nonce). Because the server seed was committed (hashed) before you played, and your client seed entered after, the casino could not have chosen outcomes — any tampering breaks the published hash.
The verification walkthrough
1. Before playing: the game shows you the hash of the current server seed. Record it (most clients keep history automatically). 2. Optionally set your client seed to anything — your randomness, their commitment. 3. Play. Each bet consumes a nonce: 1, 2, 3... 4. Rotate the seed in the fairness settings. The casino reveals the old server seed and commits a new hash. 5. Verify: hash the revealed seed (SHA-256, any online tool or one line of code) — it must equal the hash from step 1. Then feed seed + your client seed + a bet's nonce into the game's published result formula and confirm it reproduces the outcome you saw.
Serious operators provide a one-click verifier for step 5 and publish the exact formula. If recomputing a round requires reverse-engineering, the implementation has missed the point — our casino reviews note which operators make verification genuinely usable.
If you want the math: typical dice-style implementation: HMAC-SHA512(serverSeed, clientSeed:nonce) → take hex characters → convert to a number in [0, 9999] → compare against your win range. Crash games commit an entire seed chain at launch — each game's crash point derives from the previous hash, so the whole history is verifiable back to a published anchor.
What provably fair does NOT cover
1. The odds themselves. A dice game with a 2% edge provably takes 2%. Verification proves honesty, not generosity — the published edge is the price, and the games publish it precisely because the math is checkable. 2. Third-party games. Slots and live tables from external studios run on certified RNGs you cannot inspect. Provably fair is the originals' system. 3. The cashier. A provably fair game at an operator that stalls withdrawals is an honest game at a dishonest casino. Payout behaviour — the thing our reviews test with real money — remains the trust question that matters most.
Why this matters beyond crypto casinos
The commitment scheme inverts the traditional trust model: regulation says "trust the auditor," provably fair says "check it yourself." Both models work at serious operators; only one works without an institution behind it. For the games it covers, a player with one verification under their belt needs nobody's word — which is the strongest consumer position gambling has ever offered.