FREE / NO REAL MONEY
Provably Fair Verifier for Revealed Seeds
Check a published hash against a revealed seed, then reproduce supported Dice or Plinko round outcomes. Never enter unrevealed or active seeds.
How it works & examplesUnderstand the calculation
What a provably fair verifier can actually check
A verifier reproduces a completed result from the inputs used by a specified algorithm. The server seed, client seed and nonce must belong to the same round and the same implementation. A matching hash commitment checks that the revealed server seed agrees with the commitment you recorded before the round; the result calculation is a separate check.
To see what a verified roll actually means for the winning threshold and payout, compare it in Casino Dice Calculator: Win Chance, Multiplier and Virtual Rolls.
Use the Dice or Plinko algorithm explicitly supported by this tool. A result from another game, another casino or another version is not automatically comparable. Before the server seed is revealed, this verifier cannot calculate future outcomes. A matching calculation confirms that particular reproduction, not the operator's solvency, withdrawal policy or every part of its service.
Maths & verification
Verify revealed server seeds, SHA-256 commitments and published Stake-style HMAC-SHA256 Dice or Plinko rounds directly in your browser.
Try the simulator below. Input values stay in your browser; no account or money is involved.
Model assumptions: No. Virtual games use declared teaching models. Verify any actual operator’s payout rules independently.
Related interactive tools
- Casino Dice Simulator: Choose Your Win Chance
Play free virtual Dice with over/under bets, adjustable win chance, sample history, 99% model RTP and transparent multiplier maths.
- Plinko Simulator: Landing Probabilities and Demo
Drop animated Plinko balls, select risk and rows, inspect binomial landing probabilities and run 100 or 1,000 virtual trials.
- Mines Calculator: Safe-Tile Odds and Virtual Play
Calculate exact Mines survival probability, test safe picks on a playable 25-tile board and compare model payouts using virtual credits.
How to use the tool
Verify an already completed round against a previously published server-seed commitment.
- Save the originally published SHA-256 server-seed hash before rotation.
- After the operator reveals the server seed, enter it together with your client seed, nonce and supported game.
- Check the commitment match and reproduce the Dice number or Plinko route using the published byte mapping.
Understanding your result
Matching SHA-256 hashes confirm that the revealed seed equals the seed committed before play, provided you retained the original hash. A result comparison also needs the correct seed pair, nonce and algorithm version.
Scope and limitations
Only the documented Stake-style Dice and Plinko mappings are supported. This does not certify external games, live unrevealed seeds or an operator’s overall integrity.
Before you rely on the result
- How the calculation works
Formulas, assumptions, rounding and model limits are documented on the methodology page.
- Check the current inputs
Use the odds, RTP, fees, bonus terms or other values currently shown by the operator or market.
- Reference used
Provably fair verification: commitment, reveal and exact replay
A provably fair check answers a narrow question: after a server seed is revealed, does it match the commitment published before the round, and does the documented algorithm reproduce the recorded result? It does not make the hidden seed predictable.
A complete verification needs the pre-rotation commitment, the revealed server seed, the client seed, the nonce and the exact byte-to-result mapping used by the supported game.
Commitment first, reveal later
SHA-256 lets you hash the revealed server seed and compare it with the commitment saved before rotation. Matching hashes show that the revealed seed is consistent with that earlier commitment; saving the commitment only after the reveal removes the useful time-order evidence.
The same seeds can produce different game results under different mappings
HMAC output is only raw deterministic data. Dice, Plinko and other games can map bytes to outcomes differently, so reproducing a hash is not enough: the verifier must also use the documented game algorithm, client seed and nonce.
What a successful check does not prove
A matching round does not certify an operator's solvency, withdrawals, RTP claims or every game implementation. It verifies the supported commitment-and-result process for the inputs you supplied and nothing more.
Reproduce a provably-fair round
Use this when
You have the exact server/client seed inputs, nonce and algorithm used by the game.
Read the result like this
A matching result shows the published inputs reproduce the round; it does not audit the casino business or prove future rounds are fair.
Common mistake
Verifying the wrong nonce, seed order, encoding or algorithm can produce a false mismatch.
Verification workflow
- Copy the revealed server seed or server-seed hash from the round record.
- Copy the client seed and exact nonce used for that round.
- Use the operator/game algorithm and the same encoding order.
- Compare the reconstructed digest/result with the recorded game result.
Worked example
If the SHA-256 hash of a revealed server seed matches the commitment saved before rotation, the seed is consistent with that prior commitment. The nonce and client seed then let you reproduce a supported published outcome.
Can I verify an unrevealed server seed?
No. You must wait until the operator reveals the server seed; never paste an active or secret seed into a third-party tool.
Questions about this calculation
Why can’t I verify an active hidden seed?
The operator has not disclosed it yet. A one-way commitment is meant to be checked after seed rotation; never paste active private secrets.
Does a matching hash prove every bet was fair?
No. It checks a particular commitment, and round reproduction checks the specified mapping. Other claims require separate evidence.
When is Provably Fair Verifier for Revealed Seeds the right tool?
Verify an already completed round against a previously published server-seed commitment.
How should I read the result from Provably Fair Verifier for Revealed Seeds?
Matching SHA-256 hashes confirm that the revealed seed equals the seed committed before play, provided you retained the original hash. A result comparison also needs the correct seed pair, nonce and algorithm version.
What can Provably Fair Verifier for Revealed Seeds not tell me?
Only the documented Stake-style Dice and Plinko mappings are supported. This does not certify external games, live unrevealed seeds or an operator’s overall integrity.