How to verify a bet
- Find the bet in your bet history and note its client seed and nonce.
- Rotate your seed pair in the fairness settings. The casino then reveals the server seed that was in use.
- Pick the game above and paste the three values. For games with settings, enter the ones the bet was played with.
- Compare the result with the one in your bet history. They should be identical.
- Optional: paste the server seed hash you were shown before betting. If it matches the revealed seed, the casino could not have swapped the seed after seeing your bets.
New to this? Our guide to provably fair games explains what the seeds and the nonce are and what this kind of check does and does not prove.
What is covered
| Casino | Games | Method |
|---|---|---|
| Stake verifier | Dice, Limbo, Plinko, Roulette, Wheel, Diamonds, Flip, Blackjack / Hilo / Baccarat cards | HMAC-SHA256, key: server seed, message: clientSeed:nonce:round |
| Roobet verifier | Dice, Dice (older rounds), Limbo, Mines, Keno, Towers | HMAC-SHA512, key: server seed, message: "clientSeed - nonce", then a second hash per game |
| Gamdom verifier | Dice, Slide, Plinko, Mines, Keno, Blackjack cards | HMAC-SHA512, key: server seed, message: clientSeed-nonce |
| Shuffle verifier | Dice, Limbo, Plinko, Mines, Keno, Roulette, Wheel, Tower, Chicken, Coinflip, Blackjack / Hilo cards | HMAC-SHA256, key: server seed, message: clientSeed:nonce:round |
| Duel verifier | Dice, Limbo, Plinko, Mines, Keno, Blackjack / Hilo cards | HMAC-SHA256, key: server seed bytes (hex), message: clientSeed:nonce or clientSeed:nonce:cursor |
Only games played with your own seed pair are covered. Round-based games such as Crash, where every player gets the same result, use a different scheme and are not included yet.
Where the formulas come from
Every casino turns the hash into a result in its own way: which bytes it reads, how it avoids bias, how it rounds. A verifier built on a generic formula gives wrong answers, so each one here is taken from what the operator itself publishes.
- Stake: Formulas from Stake's own provably fair pages. Stake and Shuffle generate their random numbers with the same published function, so the worked examples in Shuffle's documentation test that part for both. Stake publishes no worked examples for the individual games, and its site could not be reached from where we tested, so the game formulas have not been checked against Stake's own verifier. One assumption: Stake writes its Dice formula without rounding down; we round down because it is the only reading that gives a two-decimal roll.
- Roobet: Formulas from the verifier code Roobet links from its fairness page. Dice (current and older version) and Limbo give the same results as Roobet's own verifiers on the same seeds. Mines, Keno and Towers follow the same published code, but Roobet's verifiers for them have no form to type into, so they have only been checked against a second calculation of ours.
- Gamdom: Formulas from the verifier code Gamdom links from its help centre. Dice, Slide, Plinko, Mines, Keno and Blackjack give the same results as Gamdom's own verifiers on the same seeds.
- Shuffle: Formulas from the code in the provably fair section of Shuffle's help centre. The worked examples in those articles (Dice 43.05, Limbo 2.29, Roulette 15 and the others) are reproduced exactly. Shuffle's own verifier needs an account, so we could not run it ourselves.
- Duel: Formulas from the verification code Duel shows on its own provably fair page. Every game here gives the same results as Duel's own verifier on the same seeds. Plinko buckets are counted from 1, as Duel shows them.
We are not affiliated with the operators' fairness teams and this page is not an audit of any casino. If you find a bet where this tool and the casino's verifier disagree, tell us and we will look into it.