Reading a Provably-Fair Seed: A Step-by-Step Verification
Verifying a provably-fair bet means confirming three things: that the server seed the casino revealed matches the hash it committed to before you played, that your client seed and the bet's nonce were part of the calculation, and that feeding those values into the stated hashing algorithm reproduces the exact outcome you saw. When all three line up, that bet could not have been altered after the fact. This proves integrity of a single verified bet — not that the game's odds favour you, not that the casino is licensed or solvent. Gambling carries real financial risk, is age-restricted (18+), and may be illegal where you live, so check local law first.
What is a provably-fair seed made of?
Three inputs: a secret server seed, your client seed, and a per-bet nonce counter.
Provably fair is a commitment scheme built on cryptographic hashing. Before you place a single bet, the casino generates a secret server seed and shows you only its hash — a fingerprint that is easy to produce from the seed but practically impossible to reverse. That hash is the casino's public promise: "the seed is already fixed, and here is proof I can't change it later." You supply or accept a client seed, a value you can typically edit, which guarantees the casino did not pick the seed pair after seeing your bets. Finally, a nonce — a simple counter — increments with each bet so the same seed pair yields a different outcome every round. If you are new to the concept, start with our primer on what is provably fair, then come back here for the hands-on verification.
| Input | Who controls it | Role |
|---|---|---|
| Server seed | Casino (secret until reveal) | Committed in advance via its published hash |
| Server seed hash | Casino (public up front) | Proves the seed existed before you bet |
| Client seed | You (usually editable) | Stops the casino choosing seeds after the fact |
| Nonce | System counter | Makes each bet unique under one seed pair |
Why must the server seed be revealed before you can check it?
Because it stays secret during play so outcomes can't be predicted, then is revealed on rotation.
There is a deliberate tension in the design. While a server seed is active, the casino must keep it secret — if you knew it, you could compute upcoming outcomes and the game would be broken. So during play you only ever hold the hash. To verify, you first rotate (or "seed change"), which retires the current server seed and reveals its plaintext, while a fresh hashed seed takes over for future bets. Only after the reveal can you check the old seed against its hash and recompute every bet made under it. This reveal-and-rotate cycle is the heart of the system.
How do I verify a single bet step by step?
Rotate the seed, match the hash, then recompute the outcome from seed, client seed and nonce.
Note the committed hash
Before betting, record the server seed hash the casino displays. This is the promise you will hold it to.
Record client seed and nonce
Note your active client seed and the nonce of the specific bet you want to verify.
Rotate to reveal the server seed
Trigger a seed change so the casino reveals the plaintext server seed you were playing under.
Confirm the hash matches
Hash the revealed server seed with the stated algorithm (commonly SHA-256) and check it equals the committed hash from step 1.
Recompute the outcome
Feed server seed, client seed and nonce into the casino's published formula and translate the hash output into a game result.
Compare
If the recomputed result equals what you saw, that bet was fixed in advance and untampered.
Most reputable operators publish their exact algorithm and often provide an in-house or third-party verifier, so you can paste the three inputs and see the outcome recomputed. The point of doing it yourself at least once is to confirm the verifier is real and the numbers reconcile.
How is the hash turned into a game outcome?
The combined inputs are hashed, then the hex output is mapped to a number in the game's range.
The casino concatenates the inputs in a documented order — for example server seed, client seed, and nonce joined by a separator — and runs them through a hash function like HMAC-SHA-256. The resulting hexadecimal string is deterministic: identical inputs always give the identical output. The game then converts a slice of that output into the format it needs — a roll from 0 to 99.99, a card index, a crash multiplier — using a stated method. Because every step is public and repeatable, anyone with the three inputs arrives at the same result. That determinism is precisely what makes tampering detectable.
Because you can change the client seed, the casino cannot have pre-selected a server seed that pairs badly with your bets. Rotating your client seed periodically is a normal, healthy habit and reinforces the guarantee.
What does verifying actually prove — and what does it not?
It proves one bet was committed and unaltered; it says nothing about odds, licensing or solvency.
It is easy to over-read a green "verified" checkmark. Here is the honest boundary of what a successful verification establishes:
- It proves: the specific bet's outcome was fixed before you played, was influenced by your client seed, and was not changed afterward.
- It does not prove: the game's house edge or payout odds are fair to you — a provably-fair game can still have a large built-in edge.
- It does not prove: the casino is licensed, solvent, or will actually pay your withdrawal.
- It does not prove: anything about bets you did not personally verify.
Provably fair is one pillar. Licensing, payout reliability, and reputation are separate checks — walk through all of them in our how to choose a crypto casino guide, and see how we weight each in our review methodology.