How to Verify a Provably Fair Game Yourself
Published 4 April 2026 | Reading time: 7 minutes | By James Harlow — editorial byline of this site, not an employee of any casino
"Provably fair" is one of the few claims in this industry that can be checked rather than trusted. It is also one of the most often displayed as a badge by sites that do not implement it. The difference is visible in about two minutes if you know what to look for.
The three inputs
| Element | Who controls it | Purpose |
|---|---|---|
| Server seed | The operator | The secret that determines the outcome; revealed after the round |
| Server seed hash | Published in advance | A commitment — proves the seed existed before you bet and was not changed |
| Client seed | You | Your input into the calculation, so the operator cannot pre-compute a convenient result |
| Nonce | Automatic counter | Distinguishes round 1 from round 2 with the same seed pair |
The commitment is the mechanism worth understanding. A cryptographic hash is easy to compute in one direction and infeasible to reverse, so publishing the hash of a seed reveals nothing about the seed while making it impossible to substitute a different one later. When the operator reveals the seed at the end and its hash matches what was published at the start, the seed cannot have been chosen after your bet.
Verifying a round, step by step
- Before playing, copy the published server seed hash. If none is published in advance, stop here — there is nothing to verify.
- Set your own client seed. Any string works; the point is that you chose it.
- Play the round and note the nonce.
- Rotate the seed pair. Most implementations only reveal the server seed once you request a new one.
- Hash the revealed server seed and compare it with the value you copied in step one. They must match exactly.
- Feed server seed, client seed and nonce into the site's verifier, or any independent implementation of the same algorithm, and confirm it reproduces the result you saw.
Step five is the one people skip, and it is the one that matters. Comparing the hash you saved yourself against the revealed seed is the entire proof. A verifier that only re-runs the operator's own numbers proves nothing on its own.
What the proof does not cover
This is where the marketing usually gets ahead of the mathematics:
- It says nothing about the house edge. A verifiable game can pay back 99% or 90%; the proof concerns the draw, not the paytable.
- It does not guarantee withdrawals. Cryptographic integrity and financial solvency are unrelated properties.
- It does not cover the rest of the site. One verifiable dice game does not make the slots verifiable.
- It does not prove the operator is licensed. Those are separate checks, and the licence check is about which domains a record covers.
How to spot a badge with nothing behind it
Three questions settle it. Is the server seed hash shown before the round? Can you set your own client seed? Is the server seed revealed afterwards? A site that fails any one of them is displaying a label, not implementing a protocol.
Quick answers
Do I need to be technical to check?
No. Copying a hash and comparing two strings is the whole skill required.
Is provably fair the same as certified RNG?
No. A certified RNG is audited by a testing laboratory; provably fair lets you check each round yourself. Different mechanisms, different guarantees.
Can the operator still have an edge?
Yes, and it does. The edge is in the payout rules, which are public and unaffected by verification.
What if the hashes do not match?
Then the revealed seed is not the one that was committed to. Save the values and stop playing there.
