“Provably fair” is the one claim in crypto gambling that can be checked with maths rather than trust. It is also narrower than the marketing suggests. The system lets you verify, after the fact, that a specific game result was determined by values fixed before you bet and was not altered once the operator saw your stake. It does not tell you the game pays well, it does not cover the licensed slots that make up most of any casino’s library, and it does nothing about whether your withdrawal arrives. This page explains the mechanism step by step, shows what a verification actually involves, lists which operators in our data document it, and sets out the limits plainly.
The problem provably fair solves
In a conventional online casino, the random number generator runs on the operator’s server. You see the outcome, but you cannot see how it was produced, so you rely on the regulator’s testing regime and the auditor’s certificate. With a Curaçao or Anjouan licence, both of which cover almost every operator we track, that regime is thin. Provably fair replaces trust in the auditor with a cryptographic commitment: the operator locks in its randomness before you act, you contribute randomness of your own, and the two are combined in a way anyone can recompute.
The three ingredients
Server seed
A long random string generated by the casino. Before any bet is placed, the casino publishes not the seed itself but its hash, typically a SHA-256 digest. A hash is a one-way fingerprint: it is trivial to compute from the seed, practically impossible to reverse, and any change to the seed produces a completely different hash. Publishing the hash commits the casino to that seed without revealing it.
Client seed
A string you control. Most interfaces generate one for you and let you edit it. Because the casino does not know your client seed when it fixes the server seed, it cannot choose a server seed that produces favourable outcomes for the pair.
Nonce
A counter that starts at zero and increases by one for every bet made under the same seed pair. It ensures that each bet gets a fresh result even though the two seeds stay the same for a whole session.
How a result is produced
The implementation details vary by operator, but the common structure runs as follows.
- The casino generates a server seed and shows you its hash.
- You set or accept a client seed. The nonce is 0.
- For each bet, the casino computes a keyed hash of the inputs, usually HMAC-SHA256 or HMAC-SHA512 with the server seed as the key and “client seed:nonce” as the message.
- Part of the resulting digest is converted into the game outcome. For a dice game, a slice of the hash becomes a number between 0 and 99.99. For a crash game it becomes a multiplier. For a card game it drives a shuffle.
- The nonce increases by one and step 3 repeats for the next bet.
- When you rotate to a new server seed, the casino reveals the old one. You can now hash it, confirm it matches the hash shown at step 1, and recompute every result in the session.
The commitment in step 1 is what makes the scheme work. If the casino had changed the server seed after seeing your bets, the revealed seed would not hash to the value it published in advance, and the verification would fail.
Verifying a result yourself
The casino’s own verifier is the convenient route, but it is also the party you are checking, so an independent check is better. You need four things: the revealed server seed, its published hash, your client seed and the nonce of the bet in question. The steps are the same regardless of tooling.
- Hash the revealed server seed with SHA-256 and compare it with the hash shown before the session. If they differ, stop: the commitment was broken.
- Compute the HMAC with the server seed as key and the client seed and nonce as message, using the algorithm the operator documents.
- Apply the operator’s documented conversion from hash to outcome. This step is operator-specific and must be published; without it, you can recompute the hash but not the result.
- Compare with the result you were shown.
Any programming language with a standard cryptography library can do this in a few lines, and open-source verifiers exist for the common formats. The point is not that you will check every bet, but that you could, and that the operator knows you could.
Which operators document provably fair games
Thirteen of the 35 operators in our database document provably fair games in the fetched sources: BC.Game, Cloudbet, 7Bit Casino, FortuneJack, Roobet, Vave, TrustDice, Duelbits, Rakebit, Metaspins, Coins.Game, Thrill and Betplay.io. The scope is usually limited to in-house titles. Cloudbet describes “in-house Originals with a fairness verifier”. 7Bit applies it only to crash, dice and instant-win titles. Coins.Game lists 11 provably fair originals by JetGames. For the remaining 22 operators, including Stake, BitStarz, Shuffle, Rollbit, Sportsbet.io and all six US-facing books, the field is not documented in the sources we fetched. That does not mean those sites lack the feature; it means we could not verify a published description, so we do not credit it.
Two of the thirteen are worth a second look before you treat the label as reassurance. Betplay.io documents provably fair games and has no verified gambling licence at all, only a Costa Rica company registration. Coins.Game documents them and carries a Casino Guru safety index of 1.4 with 77 complaints on file. Provable fairness of the dice roll says nothing about whether the operator pays. The licences page covers that side of the question.
What provably fair does not prove
It does not cover most of the library
Slots from Pragmatic Play, NetEnt, Evolution, Hacksaw and the other studios named across our reviews run on the studio’s own servers with the studio’s own random number generator. The casino cannot make those provably fair because it does not control the randomness. A site with 10,000 games and a dozen provably fair originals is, for practical purposes, a conventional casino with a small verifiable corner. The share of verifiable games at any operator is a question worth asking support directly.
It does not change the house edge
Verification shows the result was not tampered with. It does not show the game is good value. A provably fair dice game with a 1% house edge and a provably fair crash game with a 4% edge are both honest and both lose you money over time at different rates. The edge is set by the payout table, which is a separate published figure, and a game can be perfectly fair and perfectly expensive at the same time.
It checks the past, not the present
You can only verify a bet after the server seed has been revealed, which happens when you rotate seeds. Until then you have a hash and a promise. An operator that manipulated outcomes would be caught the moment anyone verified, which is a strong deterrent, but the check is retrospective by design.
It depends on your client seed
If you never change the default client seed, the scheme still holds in theory, because the server seed was committed before the default was assigned. In practice, setting your own seed removes any argument about who chose what. Change it at the start of a session and again when you rotate.
It does not touch the cashier
Fair results and paid withdrawals are different problems. The operators with the most documented regulatory trouble in our data, BC.Game and Vave, both document provably fair games. BC.Game’s former operators were declared bankrupt by a Curaçao court amid player claims over $2.5 million; Vave’s operator was fined EUR 3.08 million by the Dutch regulator in June 2026. Neither event had anything to do with game outcomes. The rankings on our best crypto casinos page weight trust and payments at more than half the score for that reason.
Reading a provably fair claim critically
- Is the algorithm published? A hash on screen without a description of how hash becomes outcome is not verifiable.
- Can you rotate the server seed yourself? If not, you may never see the revealed seed and can never verify.
- Which games are covered? Originals only, usually. Ask for the list.
- Is there an independent verifier? Verifying on the operator’s page proves little if the page is the thing you distrust.
- What is the house edge? Fairness and value are separate numbers.
Provably fair games are the best reason to prefer a crypto-native operator over a conventional one for dice, crash and similar titles, and the list above is where to start. For everything else, the licence, the payment terms and the bonus conditions matter more. Those are compared on the bonus terms page, the no-deposit page and, coin by coin, starting with Bitcoin casinos.
What does provably fair mean?
A game is provably fair when the operator commits to its random input by publishing a hash before you bet, you contribute a client seed, and after the server seed is revealed you can recompute every result and confirm nothing was changed once your stake was known.
Can I verify a provably fair result without the casino’s tool?
Yes. Hash the revealed server seed and compare it with the published commitment, then compute the HMAC of client seed and nonce with the server seed as key and apply the operator’s documented conversion to an outcome. Any standard cryptography library can do it.
Are slots provably fair?
Generally not. Slots from external studios run on the studio’s own random number generator, which the casino does not control. Provably fair usually covers only in-house titles such as dice, crash, plinko and similar originals. 7Bit, for example, applies it only to crash, dice and instant-win games.
Does provably fair mean the casino is safe?
No. It proves game results were not manipulated; it says nothing about licensing, withdrawals or bonus terms. BC.Game and Vave both document provably fair games and both have documented regulatory actions unrelated to game outcomes.
Which crypto casinos have provably fair games?
In our data, BC.Game, Cloudbet, 7Bit, FortuneJack, Roobet, Vave, TrustDice, Duelbits, Rakebit, Metaspins, Coins.Game, Thrill and Betplay.io document them. For the other 22 operators the feature is not described in the sources we fetched.
Does provably fair lower the house edge?
No. The edge comes from the payout table, not the randomness. A provably fair game can be honest and still carry a 1%, 2% or 4% edge, and that figure is what determines your expected loss.
Last updated: