How To Verify a Provably Fair Result Yourself

How To Verify a Provably Fair Result Yourself

The short answer

You verify a provably fair result in two checks. First, you hash the revealed server seed with a public SHA-256 tool and confirm it matches the hash the site published before your round. Second, you recombine that server seed with your client seed and the bet's nonce, then recompute the outcome to see that it matches what you were shown. If both checks line up, the result was locked in before you bet and nobody changed it afterward.

What does provably fair actually commit to?

If you're new to the idea, read our full concept explainer first. Here's the one-paragraph recap.

Provably fair uses a "commit-reveal" system. Before the round, the casino generates a secret server seed and shows you only its cryptographic fingerprint, a SHA-256 hash. That hash is the commitment. Because SHA-256 is one-way, the casino can't change the seed later without breaking the hash, and you can't read the seed from the hash in advance. After you play, the casino reveals the original seed so you can check it against the commitment yourself.

What are the moving parts?

Four pieces drive every provably fair round. Knowing who controls each one is half the battle.

The nonce matters more than it looks. It increments by one each bet, so the same seed pair produces a different, independently verifiable outcome for every round (Gamingtec, retrieved 2026-07-25).

How do you verify a result step by step?

You don't need to write code. You need a public SHA-256 or HMAC-SHA256 tool and a few minutes. The values below are illustrative, not a real bet log.

1. Save the commitment before you bet. Open the site's Fairness or Provably Fair panel and copy the published server seed hash, for example `d4f7...9c2a`. Without this, you can't prove the seed came first.
2. Set or note your client seed. Say you use `wild-academy-01`. You can rotate this anytime, which forces a fresh server seed too.
3. Play, then reveal the server seed. The seed stays hidden while it's active, by design. Rotate your seed pair to reveal the old server seed, for example `8b1e...47f0`.
4. Check the commitment. Paste that revealed server seed into a SHA-256 tool. The output must exactly equal the hash you saved in step one. If it matches, the casino committed to this exact seed before your bet.
5. Recompute the outcome. Feed the server seed, your client seed, and the bet's nonce into the game's published formula. Most sites use HMAC-SHA256 with the server seed as the key and `clientSeed:nonce` as the message, then convert the hex output to a game number (Gamingtec, retrieved 2026-07-25).
6. Compare. If your recomputed result matches the result you were shown, the round is verified. The outcome was fixed at commitment and untouched afterward.

Why does step four work? SHA-256 has an avalanche effect. Change one character of the seed and roughly half the output bits flip, so any tampering produces a wildly different hash that fails the match (The SSL Store, retrieved 2026-07-25). The full standard is published by NIST (FIPS 180-4, retrieved 2026-07-25).

What if the hashes don't match?

Don't jump straight to "the casino cheated." Most mismatches are input errors on your side.

Common causes are a wrong nonce, the wrong separator between client seed and nonce, or hashing the wrong value. A classic slip is hashing the server seed hash again instead of the raw revealed seed. Double-check that you copied the exact revealed seed, not the commitment.

If everything looks right and it still fails, try a second independent verification tool to rule out a bug in the first one. Then save screenshots of the seeds, nonce, and expected versus actual result, and raise it with the operator's support. A clean record makes your case far stronger.

What does provably fair not prove?

This is the limit people miss. Provably fair proves integrity, not profitability.

It confirms the RNG output wasn't altered after the commitment. It does not change the house edge, and it does not make a bet "fair odds." A game can be fully provably fair and still carry a built-in mathematical advantage for the house, which means a negative expected value for you over time. Verification tells you the coin flip was honest. It doesn't make a losing bet a good bet.

How is RNG certification different?

Provably fair is one trust layer. Independent RNG certification is a separate, complementary one, and it's easy to conflate them.

Labs such as iTech Labs, Gaming Laboratories International (GLI), and eCOGRA test a game's random number generator against its declared math model, checking that outputs are statistically random and match the published return-to-player figure (eCOGRA, retrieved 2026-07-25). Provably fair lets you re-check a single result. Certification is an audit of the whole system's randomness by a third party.

One caveat on certification. It's version-specific and labs don't watch every spin in real time, so a seal is a snapshot, not a live guarantee. When you're sizing up an operator, use both signals together and see our guide on how to tell if a crypto casino is legit.

Want the wider picture on crypto play? Start with what a crypto casino is, the broader crypto casino guide, and the rules around whether crypto gambling is legal. For a structured path, the Crypto for Players course walks through it.

A note on responsible play

Verification is a trust tool, not a winning strategy. No amount of hash-checking changes the house edge or your odds. Set limits before you play, treat any spend as entertainment, and use the responsible gambling tools if play stops feeling fun.

Run the verification in our provably fair calculator — all computation happens in your browser.