Provably fair verification
Updated 13 Nov 2026 · 6 min read
A provably fair game hands you three values for every bet and a formula that joins them. With those you can rebuild the result on your own device and see whether the casino kept its word. This guide walks through provably fair verification for one bet, from the fingerprint you saw before betting to the number the game showed.
Three values, and who controls each of them
The server seed belongs to the casino. While it is in use you only see its fingerprint, a hash of 64 characters. The client seed belongs to you, and most games let you type your own. The nonce is a plain counter that moves up by one with each bet.
The order of events is the whole point. The casino fixes its seed and shows the fingerprint first. You add your seed second. Neither side can pick a result alone, because neither knows the value of the other in time. The glossary of fairness terms defines each word in a line or two.
Step one: test the promise made before the bet
Copy the hash of the server seed before you play and keep it somewhere. When you are done with that pair of seeds, ask the game for a new one. The old server seed is then shown in full.
Run the revealed seed through SHA-256 and compare the output with the fingerprint you kept. All 64 characters must be equal. A seed that differs by a single letter produces a completely different hash, so a near miss does not exist. It fits, and the seed was fixed before your bets, or it does not.
Step two: rebuild the number the game showed
A common scheme for dice works like this. The server seed is used as the key of an HMAC, and the message is your client seed and the nonce joined by a colon. The output is another long hash, and only its first 4 bytes are used.
Say those bytes are 97, 30, 184 and 81, written 611eb851 in the hash. The first is divided by 256, the second by 256 twice over, and so on, and the pieces are added up. The first byte alone gives 0.378906, and all four give 0.379375. That is a fraction between zero and one, and the same seeds produce it every time.
The last step stretches the fraction over the outcomes of the game. A dice roll from 0.00 to 100.00 has 10,001 possible results. So the fraction is multiplied by 10,001, which makes 3794.13. The decimals are cut off and the rest is divided by 100. The roll is 37.94.
Why the nonce deserves a second look
One pair of seeds serves many bets, and the nonce is the only thing that changes between them. Enter a nonce that is off by one and you rebuild a neighbouring bet, with a result that has nothing in common with yours.
Counting does not start at the same place everywhere: the first bet on a new pair may carry 0 or 1. If a check fails, try the number above and the number below before you suspect anything else.
Games that need a formula of their own
The two steps are alike everywhere, and the cut from hash to result is not. A crash round, a Mines board and a Plinko path each read the hash in their own way. Aviator goes further and mixes the seeds of several players into one round. That is why it has a verifier built for Aviator rounds and a guide on checking that an Aviator round was fair.
For a long list of finished bets, the bulk verifier repeats the check line by line, and how to check a whole bet history explains how to read what it returns. The chance behind a dice roll, as opposed to its honesty, is the subject of the dice calculator.
What a passed check is worth
A pass tells you two things. The casino committed to its seed before you bet, and the result follows from the seeds by the published formula. It cannot tell you that the formula is generous. The house edge sits inside the formula, in how the fraction is turned into a win or a loss.
A check also works only backwards. While a server seed is live you hold its fingerprint and nothing more, so no bet can be computed ahead of time.
Questions about provably fair verification of one bet
What do I need to verify a provably fair bet?
The revealed server seed, your client seed, the nonce of the bet and the result the game showed. The hash saved before betting lets you test the commitment as well.
Where do I find the server seed after a bet?
In the fairness or seed settings of the game. It appears in full once you switch to a new pair, and until then only its hash is visible.
My recomputed result is different. Did the casino cheat?
Not on that evidence alone. First rule out a wrong nonce, a stray space in a seed and a casino formula that differs from the generic one. A seed that fails its own hash is the clear sign.
Can I change my client seed?
In most provably fair games, yes, at any moment between bets. Changing it usually opens a new pair of seeds, and the counter starts again.
What does the nonce do in a provably fair bet?
It tells apart the many bets made on one pair of seeds, rising by one with each bet. A nonce that is off by one rebuilds a neighbouring bet with an unrelated result. Games do not all start counting at the same number, so try the one above and the one below when a check fails.
Tools for recomputing a result
More guides
- Aviator predictor: why no prediction app can work
- Aviator provably fair: how to check a round
- RTP in crash games: what the figure means
- Martingale strategy on crash games: does it work?
- Mines strategy: how many mines to pick
- Plinko odds and risk levels explained
- Betting odds explained: decimal, fractional, American
- What bookmaker margin is and how to find fair odds
- The Kelly criterion explained with worked examples
- How arbitrage betting works and where it goes wrong
- How to check a bet history for fairness
- Max win odds: how rare the top multiplier is
- Losing streak odds: the chance of N losses in a row
- Risk of ruin: how long a casino bankroll lasts
- Expected loss: what a casino session costs on average
- House edge on casino games: why similar titles differ
- Bitcoin bet units: BTC, mBTC, bits and satoshi
Games