Provably Fair: What It Is and How to Verify It Yourself

"Provably fair" is crypto gambling's biggest innovation: a mathematical system that lets you check, bet by bet, that the outcome wasn't tampered with. Here's how it works under the hood.

The idea in 30 seconds

Before each round, the casino publishes the hash (a SHA-256 cryptographic fingerprint) of its secret seed. You contribute your own seed from the browser. The outcome comes from combining both with a counter (nonce). Because the hash was published before you bet, the casino can't swap its seed afterwards without the fingerprint failing to match — cheating would expose itself.

How to verify a bet

1. After the round, open the bet details and find the revealed server seed, your seed and the nonce.
2. Run the server seed through a SHA-256 generator (online verifiers exist) and confirm it matches the hash published before you played.
3. Combine seeds and nonce with the game's formula — most casinos include a verifier that does it for you — and confirm it reproduces the exact result.

What provably fair covers (and what it doesn't)

It applies to the casino's own "originals": Dice, Crash, Plinko, Mines… Third-party slots (Pragmatic, NetEnt…) don't use this system; their randomness is guaranteed by independent RNG audits instead. That's why we assess both seals separately in every review.

Where it's done best

Duel is the current benchmark: all its Originals are provably fair with SHA-256 seeds and publish a 99.9% RTP. CYBet and Betpanda also offer verifiable originals. The full comparison is in the ranking.

Frequently asked questions

Does provably fair guarantee I'll win?

No. It guarantees the outcome was random and untampered; the game's house edge still exists and is published in its RTP.

Do I need to code to verify?

No: serious casinos include a verify button that runs the math for you. Understanding what it checks — that the prior hash matches — is all you need from this guide.

Can I change my seed?

Yes, and it's worth doing occasionally: rotating your client seed forces the server to reveal its seed and commit to a new one, closing the verification loop.