Provably Fair Checker
Reproduce one finished bet from its revealed server seed, client seed and nonce, and see at which stage a mismatch begins.
How to verify a provably fair bet step by stepRuns in your browser. Nothing you enter is uploaded.
Never paste an active, unrevealed server seed.
Bet details
Paste bet JSON or add a round ID
Your result appears here
Fill in a finished bet on the left, or load the sample.
- Waiting
Stage 1 · Commitment
Hashes the revealed server seed and compares it with the hash you saved before the bet.
- Waiting
Stage 2 · HMAC
Mixes the server seed with your client seed and nonce to get the bytes behind the result.
- Waiting
Stage 3 · Mapping
Turns those bytes into the game's number and compares it with the one the casino showed.
- Waiting
Stage 4 · Payout
Recomputes the payout from the rules and your stake, if you entered one.
How to use the provably fair checker
You need three inputs from a finished bet: the revealed server seed, the client seed and the nonce. To check the last stages too, add the result and payout you were shown. Ideally you also saved the commitment hash before you played.
Choose the preset or enter custom rules. Paste your values as plain text to run the check. The page reports each stage in order and marks the first one that does not match. Calculations stay inside your browser. Your seeds never leave the page.
The checker only works on a revealed server seed. Active seeds stay secret until rotated. Never paste an active seed into any website.
What does a provably fair calculator check?
A provably fair game commits to a secret before you bet, then reveals it so you can reproduce the result. The checker repeats the same chain in four stages:
- Commitment. Hash the revealed server seed with SHA-256 and compare it with the hash you saw before the bet. SHA-256 is defined in FIPS 180-4.
- HMAC. Use the server seed as the key and a message built from the client seed, the nonce and a counter. HMAC is defined in RFC 2104.
- Result. Turn the HMAC bytes into a number and map it to the game outcome by the operator's published rule.
- Payout. Compare the result with the bet condition and the payout you received.
A worked example you can run
Our walkthrough uses a fictional teaching round. The server seed is the text 0123456789abcdef repeated four times, the client seed is glass-board and the nonce is 7.
- The SHA-256 of the server seed starts
a8ae6e6eand endsf77c8e, which is the commitment saved before the round. - The HMAC-SHA256 message is
glass-board:7:0. The server seed is the key. - The first four output bytes are
a1 42 64 23, which, read as a big-endian integer, equal 2,705,482,787. - Divide by 2^32 = 4,294,967,296 and you get about 0.6299193.
- Shuffle documents its Dice result as the fraction times 10,001, rounded down, divided by 100. Here that is 6,299 / 100 = 62.99.
Enter the same values and the checker should show the same roll. Then change only the recorded roll to 62.98. The commitment and the reproduced roll still match, and only the comparison with the receipt fails. A failure there points at the receipt, and the calculation behind it holds up.
Where a mismatch starts
The first failing stage narrows the cause. Four common cases:
- Commitment fails: the seed belongs to a different seed pair, or it was copied with a space or line break.
- HMAC output differs: the client seed or nonce is wrong, or the separator or counter in the message is not the one the operator uses.
- Result differs: the byte-to-number step or the game mapping differs from the game's documentation.
- Payout differs: the bet condition, the multiplier rule or the rounding is not the one that applied to your bet.
Our guide on how to verify a provably fair bet lists the mistakes that create false mismatches.
What the checker cannot do
You cannot check an unrevealed seed, and a hash will not predict future rolls. The checker does not improve your odds or lower a house edge.
A matching result has strict limits. It shows the result follows from the seeds and the published rules. It does not show that the game is generous, that the multiplier table is fair or that the operator pays withdrawals. Our guide on what provably fair gambling does and does not prove covers why a green tick never guarantees a trustworthy casino.
Because operators build different schemes, accurate checks depend on entering exact rules. Take them from the operator's own documentation. Shuffle's are on its provably fair implementation page.
How this connects to the other fairness tools
Turning a hash into a game outcome is separate from calculating the game's house edge. The Mines calculator and the Plinko simulator break down the odds behind those outcomes. The sample Dice walkthrough uses this checker's example values.
Use this tool to audit past outcomes; it offers no edge on future bets. Gambling is for adults only, and the responsible gambling page lists where to get help.
Frequently asked questions
It is a tool that repeats the calculation a casino published for one of its games, using the seeds from your bet, and shows whether the result matches what you were shown. Ours checks the SHA-256 commitment, recomputes the HMAC-SHA256, converts the bytes into the game result and compares the payout, stage by stage.
No. Until the operator reveals the server seed, usually after you rotate your seed pair, there is nothing to hash or compare, and an active seed should never be pasted into a website. Wait until the bet belongs to a retired seed pair, then check it.
No. Every calculation runs in your browser and your seeds never leave the page.
Save the commitment hash before playing. Once the server seed is revealed, enter it here alongside your client seed and nonce. The checker walks through hash, HMAC, result and payout in order. Our step-by-step verification guide explains each stage and the mistakes that cause false mismatches.
The commitment only proves the server seed is the one promised. The result also depends on the client seed, the nonce and the game's mapping. If the hash matches and the result does not, compare the client seed and nonce with your bet history first, then check you used the rules for the exact game and date.
It has one preset, the Dice game as Shuffle documents it, and a custom-rules mode where you enter another operator's published scheme. Because the tool never guesses a scheme, you can only verify games where the operator publishes the exact steps.