Provably fair games explained
Provably fair lets you check that a casino result was locked in before you bet and could not be changed afterwards. It is clever and useful, but it has limits: it does not change the house edge, and it says nothing about whether a casino pays out.
The problem provably fair solves
With a normal online game you have to trust that the result was random. The casino's server rolls the number, shows you the outcome, and you have no way of checking that it did not peek at your bet first. Provably fair is a method borrowed from cryptography that removes that blind trust for one specific question: was this result fixed in advance, before I placed my bet, and could the casino have changed it?
It does that with a simple idea. The casino commits to a secret before you play, publishes a fingerprint of that secret, and reveals the secret afterwards. You check the fingerprint matches and recompute the result yourself. If it all lines up, the casino could not have altered the outcome after seeing your bet.
The three ingredients
Server seed
A long random string generated by the casino. It is kept secret while you play with it, because if you knew it you could predict every result.
Server seed hash
Before you play, the casino shows you a hash of the server seed, usually SHA-256. A hash is a one-way fingerprint: easy to compute from the seed, practically impossible to reverse, and any change to the seed produces a completely different hash. Showing the hash locks the casino in without revealing the seed.
Client seed and nonce
The client seed is a string you control. Most sites generate one for you, but you can change it to anything you like. Because the casino has already committed to its server seed before you pick yours, it cannot tune the server seed to your choice. The nonce is a counter that goes up by one with each bet (0, 1, 2…), so every bet with the same seed pair gives a different result.
How a result is generated, step by step
Implementations differ, but most crypto casinos follow this pattern:
- The casino generates a server seed and shows you its SHA-256 hash.
- You set or accept a client seed.
- For each bet, the casino computes HMAC-SHA256(server seed, client seed:nonce). HMAC mixes the inputs into a 64-character hex string that looks random.
- The game converts part of that string into a number. A common method takes the first 8 hex characters, turns them into an integer, and divides by 232 to get a value between 0 and 1.
- That value is mapped to the game: a dice roll, a crash point, mine positions, a plinko path.
- When you rotate to a new seed pair, the casino reveals the old server seed. You hash it, confirm it matches the hash shown earlier, and recompute any of your bets.
Worked example (dice, 0 to 99.99):
- Server seed (revealed after rotation):
7f3a9c1e5b2d8f40 - SHA-256 of that seed:
8dafb83e…b9227ecf, which must match the hash you were shown before playing - Client seed:
lucky-penguin, nonce:42 - HMAC-SHA256(server seed, "lucky-penguin:42") starts
ea61af90… - First 8 hex characters
ea61af90= 3,932,270,480 in decimal - 3,932,270,480 ÷ 4,294,967,296 = 0.91555…, × 100 = 91.55
If the casino's history shows a roll of 91.55 for bet 42, the result checks out. Real server seeds are much longer than this one; we shortened it so the example stays readable.
Provably fair originals
Provably fair is mostly used for in-house games, often called "originals":
- Dice: roll over or under a target. The payout multiplier is set so the house keeps a fixed edge, often around 1%.
- Limbo: pick a target multiplier; a random multiplier is generated and you win if it beats yours.
- Crash: a multiplier climbs until it "crashes". Because every player shares the same round, crash games usually use a hash chain: millions of hashes generated in advance, each derived from the next, played in reverse order. The casino publishes the final hash of the chain up front, sometimes mixed with a public value like a future block hash, so it cannot pick crash points round by round.
- Mines: the hash decides where the mines sit on the grid before you click anything.
- Plinko: the hash decides left or right at each peg.
- Keno, wheel, towers, hilo: same principle, different mapping.
These games are simple, fast and often carry a lower house edge than slots. They are also easy to play very quickly, and fast games turn a small edge into a large loss over a session. More on that below.
What provably fair proves, and what it does not
| It proves | It does not prove |
|---|---|
| The result was fixed before you bet | That the game has a fair house edge or a good RTP |
| The casino did not change the result after seeing your bet | That third-party slots or live games are fair (they use their own certified RNGs) |
| Your result follows the published algorithm | That the published algorithm maps results evenly unless you read the code |
| Each bet can be checked independently | That the casino will actually pay your withdrawal |
The house edge is built into the payouts, not hidden in the randomness. A provably fair dice game with a 1% edge will take about 1% of everything you wager over time, exactly as designed. Provably fair confirms you are playing the game as advertised, and the advertised game still favours the house. Our RTP guide explains how to turn an edge into an expected loss: wager $10,000 at 1% and the expected cost is $100.
It also says nothing about the business behind the game. A casino can run perfectly verifiable dice and still delay withdrawals, void winnings under vague terms or vanish. Licensing, reputation and how complaints are handled matter just as much. See casino licences and casino complaints.
Third-party slots from studios like Pragmatic Play or Hacksaw are not provably fair in this sense. Their fairness relies on RNG testing by independent labs and the regulator. That is not worse, just a different model of trust.
Why the commitment cannot be faked
The whole scheme rests on one property of SHA-256: nobody can find a second seed that produces the same hash. If the casino showed you hash A, then later tried to reveal a different seed that gave it a better outcome, that seed would hash to something other than A and the mismatch would be obvious. The casino could, in theory, generate millions of seeds before committing and pick a favourable one, but your client seed is added afterwards, which scrambles every result it could have planned for.
That is why the client seed matters even if you never change it from the default. It is the part the casino does not control at the moment it commits.
How to verify a bet yourself
- Before playing, open the fairness settings and copy the current server seed hash. Set your own client seed if you like.
- Play and note the nonce of any bet you want to check. Bet history usually shows it.
- Rotate the seed pair. The casino reveals the previous server seed and shows a new hash for the next one.
- Check the hash. Run SHA-256 on the revealed server seed with any independent tool and confirm it matches what you copied in step 1. This is the most important step.
- Recompute the result with the casino's verifier, or better, an independent script or third-party verifier that follows the casino's published algorithm.
- Compare the recomputed outcome with your bet history. Any mismatch is worth raising with support, with screenshots.
A casino's own verifier page is convenient but it is still the casino's code. Checking the hash with an outside tool is what gives the method its value.
Things to keep in mind
- Changing your client seed or "resetting" after losses does not change your odds. Every outcome is equally random, and patterns in past results predict nothing.
- Auto-bet and very fast games multiply volume. At 1,000 bets an hour on $1 stakes and a 1% edge, expected loss is $10 an hour; at $10 stakes it is $100. No betting system changes that.
- Rotate your seed from time to time so you can actually verify; an unrevealed server seed cannot be checked.
- Set limits before you start. Our bankroll management guide covers how.
Cashback is one of the few things that genuinely reduces the cost of play, since it returns a share of net losses whatever games you choose. Gambbly pays 10% of monthly net loss (15% at VIP level) in USDC at partner casinos including Rainbet and Wolf, on top of the casino's own rakeback. Some well-known originals casinos, like BC.Game, are not Gambbly cashback partners, so check the list first.
FAQ
What does provably fair mean?
The casino commits to a hidden server seed by publishing its hash before you play. After you rotate seeds it reveals the seed, so you can confirm the hash matches and recompute every result.
Does provably fair mean the game has no house edge?
No. The edge is built into the payouts. A provably fair dice game with a 1% edge still takes about 1% of everything wagered over time.
Are slots provably fair?
Most third-party slots are not. They rely on certified random number generators tested by independent labs, rather than seed-based verification.
Can changing my client seed improve my luck?
No. Any client seed produces equally random results. Its purpose is to stop the casino from choosing a server seed that suits your bets.
Why do I need to rotate my seed to verify bets?
The server seed stays secret while it is in use. It is only revealed when you rotate to a new pair, and you need it to check the hash and recompute results.