We built the biggest independent provably fair verifier on the market. The BTCGOSU checker currently supports 27 casinos and 51 games, with more added regularly.
As a player, the fear of a casino manipulating results is real, but provably fair removes it. Using our provably fair checker, you can verify that every bet and payout is exactly what the casino says it was. Before you start, you’ll need your server seed, client seed, and nonce from your bet history.
Is the tool not working? Please send us an email stating the issue:admin@btcgosu.com. Thanks!
Most casinos offer their own verification tool, but running a check through the casino’s own system and running one independently aren’t the same thing. BTCGOSU’s verifier reproduces the cryptographic calculation on our own infrastructure, not the casino’s, so the output can’t be influenced by the operator. If both produce the same result, you have stronger proof the outcome was fair than a casino-side check alone can give you.
The tool was built in-house rather than sourced from a third-party script, which means we control what it does and how it’s updated. We’ve run 7,248 rounds across three provably fair crash games through it, comparing actual results against theoretical distribution to test the tool and the casinos at the same time. All three tracked within 1-2 percentage points of theoretical expectation at every threshold. One finding stood out, and if you want the full breakdown it’s in our analysis of 7,248 crash rounds and our guide to the best provably fair casinos.
The tool currently supports the following casinos and games, updated regularly as we verify new additions. If yours isn’t listed, contact us via Telegram and we’ll look at adding it.
| Casino | Games Supported |
|---|---|
| BC.Game | Hash Dice, Limbo, Crash, Classic Dice |
| BitDice | Dice |
| BitKong | Mines |
| Bitsler | Dice, Blast, Roulette, Twist |
| bustabit | Crash |
| bustadice | Dice |
| Chips.gg | Dice |
| CryptoGames | Dice, Slot, Blackjack |
| CyberDice | Dice |
| DuckDice | Dice |
| FortuneJack | Dice |
| FreeBitco.in | Dice |
| Gamdom | Crash, HiLo, Roulette |
| LuckyBit | Dice, Plinko |
| LuckyDice | Classic Dice, Digital Dice |
| MintDice | Dice, Plinko |
| NitrogenSports | Dice |
| OneHash | Dice, Moon, Slots |
| PrimeDice | Dice |
| Roobet | Dice, Crash, Roulette |
| SimpleDice | Dice |
| Stake | Dice, HiLo, Diamonds, Limbo, Plinko |
| Tower.Bet | Wheel, HiLo, Crash |
| TrustDice | Dice, Crash |
| WinDice | Dice, Crash |
| Wolf.Bet | Dice |
| YoloDice | Dice |
The tool supports 27 casinos across dice, crash, roulette, HiLo, plinko, mines and more. Select your casino from the dropdown and the supported games will populate automatically.
You’ll need three values from the bet you want to verify, all available in your account on the casino. The server seed is generated by the casino before the round and shown to you as a hashed fingerprint, with the unhashed version revealed after the round ends. The client seed is your input into the result, usually set automatically but customisable before you play. The nonce is a counter that increments by one with every bet you place on a given seed pair. You’ll find all three in your bet history or fairness section, usually by clicking the shield icon next to any completed bet or navigating to account settings.
Select your casino and game from the dropdowns, then enter the unhashed server seed, the hashed server seed if you have it, your client seed, and the nonce. The hashed server seed field is optional but it lets the checker confirm the hash matches before the result is calculated, which adds a layer of confidence on top of the output.
The calculator reproduces the same cryptographic calculation the casino ran when the round was generated, independently and on our infrastructure. If the result matches what the casino recorded, the outcome was determined before the round started and wasn’t changed. If it doesn’t match, check your inputs first as a wrong nonce or mismatched seed pair is the most common cause, and if everything looks correct, see the section below.
Start by checking your inputs before drawing any conclusions. A wrong nonce, a mismatched seed pair, or the wrong game selected are the most common causes of an apparent mismatch and account for the majority of discrepancies we see reported.
If the inputs are correct and the results still don’t match, document everything before you do anything else. Save both seeds, the nonce, the casino’s stated result, and the tool’s output, and take a screenshot if possible. Contact the casino directly with the discrepancy as a formal complaint rather than a general query. If you don’t get a satisfactory response, report it to us via Telegram with your documentation. A verified mismatch after ruling out input error is a serious finding and should be treated as one. You can also read more about how we handle casino disputes.
If you want to understand the system behind what the tool is calculating, the full explanation is on our provably fair guide.
No. A casino’s verification tool works through their own system. BTCGOSU’s verifier reproduces the result independently, running the calculation on our infrastructure rather than theirs. That means the casino can’t influence the output. If both tools produce the same result, you have stronger proof the outcome was fair than if you’d only used the casino’s tool.
27 casinos and 51 games currently. The full list is in the table above. If your casino isn’t supported, contact us via Telegram and we’ll look at adding it. We add new casinos and games regularly as we verify their provably fair setups.
No. The verifier is free and open to anyone. You do need the seeds and nonce from a real bet to verify, which means you’ll need a casino account to access those. But the tool itself requires no registration.
Check your inputs first. A wrong nonce or mismatched seeds are the most common cause. If the inputs are correct and the results still don’t match, document everything and contact the casino as a formal complaint. Report to us via Telegram with your documentation. A verified mismatch after ruling out input error is a serious finding.