How to Verify a Provably Fair Bet: A Step-by-Step Guide

Verifying a provably fair bet takes about 30 seconds and three checks. First, confirm the server seed hash the casino showed you before the round matches the server seed it revealed after — hash the revealed seed yourself and compare. Second, re-run the combination of server seed + client seed + nonce through the casino's algorithm (or an open-source verifier) to regenerate the outcome. Third, confirm that regenerated outcome matches what the game actually showed you. If all three line up, the result was locked in before you bet and was not altered. This guide walks through each step for dice, crash, and mines.

Before You Start: What Verification Actually Proves

A quick but important framing point. Verifying a provably fair bet proves one specific thing: the result of that round was committed to before you placed your bet and was not changed afterward. That is genuinely valuable — but it is also narrow.

It does not prove the game's long-run RTP is honest, that the house edge is reasonable, or that the casino will pay your withdrawal. If you want the full picture of what provably fair does and does not guarantee — including the "99% RTP" marketing trap that catches a lot of players — read our companion explainer first: Provably Fair Explained: How Blockchain Verification Works and Where It Falls Short. This guide is the practical, hands-on follow-up to that one.

With that said — let's verify a bet.

The Four Ingredients You'll Be Checking

Every provably fair round is built from four components. You'll touch all of them during verification, so it helps to know what each one is:

Server seed — a secret random string the casino generates. Before the round, you only see a hash of it. After the round, the casino reveals the real seed.
Server seed hash — the SHA-256 fingerprint of the server seed, shown to you before you bet. This is the casino's pre-commitment: it locks the casino into one specific seed without revealing it.
Client seed — a value you control (or your browser generates). Because the casino can't predict it, it can't pre-pick a seed that produces a result it likes.
Nonce — a counter that increases by 1 with every bet, so each round produces a unique outcome even when the seeds stay the same.

Verification is simply the act of putting these back together yourself and confirming the math matches.

Step 1: Locate Your Seed Data

Before you can verify anything, you need to find the data. In most crypto casinos this lives in a "Provably Fair", "Fairness", or "Verify" menu — often reachable by clicking your bet in the game history, or from your account settings.

You're looking for a panel that shows:

The active server seed hash (shown now, while the seed is still secret)
Your current client seed
The current nonce (or the nonce of the specific bet you want to check)

Tip: Many platforms let you set your own client seed. Doing this before you play is good practice — it removes any doubt that the casino chose an input it preferred. Type in something random and memorable.

Step 2: Rotate (Reveal) the Server Seed

Here's the part players most often get wrong: you usually cannot verify a bet while its server seed is still active. The seed has to be revealed first, and revealing it is something you trigger.

Look for a "Rotate seed", "Reveal server seed", or "Change seed pair" button. Clicking it does two things:

It permanently reveals the old server seed — the one tied to every bet you made on that seed pair.
It starts a new seed pair (with a fresh hash) for your future bets.

This sequencing is the whole security model: the casino commits to the seed via the hash before play, and only reveals it after you've moved on. That gap is what makes cheating detectable. If a casino ever shows you a server seed before the bets tied to it are finalized, that's a serious red flag.

Once rotated, copy down the now-revealed server seed.

Step 3: Confirm the Hash Matches (the Commitment Check)

This is the first of the two real checks, and it's the most important one.

You have two things now:

The server seed hash the casino showed you before you played (Step 1).
The actual server seed the casino revealed after (Step 2).

The claim being tested: the hash shown earlier really is the SHA-256 fingerprint of this exact seed. If it is, the casino genuinely committed to this seed in advance and couldn't have swapped it.

To check it: run the revealed server seed through any SHA-256 calculator — the casino's built-in verifier, or any reputable open-source SHA-256 tool — and compare the output, character for character, against the hash you were originally shown.

✅ They match exactly → the casino did not swap the seed. The commitment holds.
❌ They don't match → the casino showed you a hash that has nothing to do with the seed it actually used. That means the outcomes could have been fabricated. Stop playing there immediately.

This single check is the backbone of provable fairness. Everything else builds on it.

Step 4: Regenerate the Outcome (the Result Check)

Now confirm that the result you saw is the result the inputs produce.

The casino's algorithm combines your three inputs — server seed + client seed + nonce — and runs them through a hash function (usually HMAC-SHA256) to produce a number, which is then converted into a game outcome.

You have two practical options:

Use the casino's own verifier. Most provably fair casinos have a verification page where you paste in the server seed, client seed, and nonce, and it recomputes the outcome.
Use an independent third-party verifier. This is the stronger choice, because it doesn't rely on the casino's own code. Several open-source provably fair checkers exist that support common game types and major operators. Using one means you're trusting public, inspectable code rather than the casino's.

Paste in your three values, run it, and you'll get a regenerated outcome.

Step 5: Compare — Does It Match What You Saw?

The final step. Compare the outcome the verifier produced against what the game actually displayed during your bet.

✅ Match → fully verified. The result was pre-committed, untampered, and correctly derived from the inputs.
❌ Mismatch → the displayed result did not come from the inputs the casino claims. Treat this as a major integrity failure.

That's it. Hash matches, outcome regenerates, regenerated outcome matches what you saw — the round is provably fair.

Game-Specific Notes

The five steps above are universal, but the outcome conversion in Step 4 differs by game.

Dice

The simplest game to verify, because the outcome is a single number. The hash output is converted into a roll — typically between 0 and 99.99. Your verifier produces that number directly; you just compare it to the roll you saw and check it against your bet (e.g. "roll under 65").

Crash

Slightly more involved. The hash output is converted into a multiplier using a specific formula, and the result is the point at which the round "crashed." Note that some crash implementations include a built-in instant-bust condition for a small fraction of rounds — this is part of the published math, not a bug, but it's a reason to read the casino's documented algorithm rather than assume.

Mines

Here the hash output is used to determine the positions of the mines on the grid. A good verifier will reproduce the full mine layout from your seed trio, which you then compare against where the mines actually were.

In all three cases the verification logic is identical — only the final hash-to-outcome conversion changes, and a decent verifier handles that conversion for you once you select the game type.

Common Verification Mistakes

A few things trip people up:

Trying to verify before rotating the seed. The server seed must be revealed first (Step 2). An active seed can't be checked.
A mismatched client seed or nonce. Verification is exact. One wrong character, or the wrong nonce, and nothing will match — even on a perfectly fair bet. Copy values precisely.
Only ever using the casino's own verifier. It's convenient, but it's the casino's code. For anything you genuinely want to be sure about, cross-check with an independent open-source tool.
Assuming verification covers RTP. It doesn't. Verifying a bet confirms that one round was untampered. It says nothing about the long-run payout percentage — that needs a separate statistical audit by a lab like eCOGRA or GLI.

Verification Is One Check Among Several

Knowing how to verify a bet is a genuinely useful skill — it moves you from trusting a casino to checking it. But verification alone is not a complete safety net, and treating it like one is itself a mistake.

A casino can serve perfectly verifiable rounds and still trap you with a 60x bonus rollover, a buried withdrawal cap, or a KYC loop that stalls your payout after a big win. Provably fair verification simply isn't designed to catch any of that. For the full set of traps that cost players the most — and how to dodge them — see Top 5 Mistakes Players Make When Choosing a Casino. Verification belongs in your toolkit alongside checking licensing, reading withdrawal terms, and confirming a real payout track record.

Think of it this way: verifying a provably fair bet proves the dice weren't loaded on that roll. The 5 Mistakes guide helps you confirm you walked into a fair casino in the first place — and our Provably Fair Explained breakdown shows you exactly where the line between those two things sits.

FAQ

How long does it take to verify a provably fair bet?Around 30 seconds once you know where the seed data lives. Locate the seeds, rotate to reveal the server seed, check the hash, regenerate the outcome, compare. The first time is slower because you're learning the casino's menu layout.

Do I have to rotate my seed to verify a bet?Yes, in almost all implementations. The server seed stays secret while it's active, and verification needs the revealed seed. Rotating reveals the old seed and starts a fresh pair — so verify in batches rather than after every single bet.

Can I verify a bet without trusting the casino's own tool?Yes, and you should. Independent open-source provably fair verifiers let you recompute outcomes using public, inspectable code instead of the casino's. Cross-checking with one is the strongest form of verification.

What if the hash doesn't match the revealed seed?That's a serious red flag. It means the pre-commitment the casino showed you didn't correspond to the seed actually used, so outcomes could have been fabricated. Stop playing on that platform.

Does verifying a bet mean the casino is fully trustworthy?No. It proves one round wasn't tampered with. It does not prove the RTP is honest, the bonus terms are fair, or that withdrawals are reliable. See our Provably Fair Explained article for what verification does not cover, and the 5 Mistakes guide for the wider checklist.

Which games can be verified this way?Provably fair verification typically applies to in-house "Originals" — dice, crash, mines, plinko, limbo, hi-lo and similar. Third-party slots on the same site usually don't use provably fair systems and rely on standard RNG certification instead.

This article is for informational purposes only and is not financial, legal, or gambling advice. Gambling carries financial risk and can be addictive. You must be of legal age in your jurisdiction, and online gambling is restricted or illegal in some regions — check your local laws. If gambling is affecting you or someone you know, contact a local support service such as BeGambleAware or GamCare.

‍

Fusce pellentesque eros sed luctus sagittis. Praesent in neque purus. Suspendisse potenti. Maecenas eget consequat lacus. Phasellus malesuada felis quam, nec gravida sapien fermentum eget. Sed tellus felis, maximus eget lorem eu, ultricies euismod libero. Integer euismod ex tellus, quis vulputate lectus placerat id. Sed eget augue sodales, fringilla nibh scelerisque, feugiat enim.

How to Verify a Provably Fair Bet - Step-by-Step