Stake Dice Verifier
Verify a dice roll (0.00–100.00) from the HMAC-SHA256 byte stream and see the exact 99 ÷ chance payout.
loading verifier…
How Dice works. How to verify it.
One float per bet: the first 4 bytes of HMAC-SHA256(server seed, client:nonce:0). Multiply by 10001, floor, divide by 100. "Roll under 49.50" wins when the number is below 49.50.
Targets at a glance
| Target | Win chance | Multiplier | Expected gap |
|---|---|---|---|
| Under 0.01 | 0.01% | 9900x | ~10,000 games |
| Under 1 | 1.00% | 99.00x | ~100 games |
| Under 2 | 2.00% | 49.50x | ~50.0 games |
| Under 5 | 5.00% | 19.80x | ~20.0 games |
| Under 10 | 10.00% | 9.90x | ~10.0 games |
| Under 15 | 15.00% | 6.60x | ~6.7 games |
| Under 20 | 20.00% | 4.95x | ~5.0 games |
| Under 25 | 25.00% | 3.96x | ~4.0 games |
| Under 33 | 33.00% | 3.00x | ~3.0 games |
| Under 49.5 | 49.50% | 2.00x | ~2.0 games |
| Under 50 | 50.00% | 1.98x | ~2.0 games |
| Under 66 | 66.00% | 1.50x | ~1.5 games |
| Under 75 | 75.00% | 1.32x | ~1.3 games |
| Under 90 | 90.00% | 1.10x | ~1.1 games |
| Under 98 | 98.00% | 1.01x | ~1.0 games |
Under 25 equals Over 75, Under 10 equals Over 90: same win chance, same payout, just different sides of the roll. No edge either way.
The byte stream behind every Original
Stake derives outcomes from HMAC-SHA256(key = server seed, message = clientSeed:nonce:round). Each round yields 32 bytes; a float is four bytes read as b₀/256 + b₁/256² + b₂/256³ + b₃/256⁴. Dice reads as many floats as it needs, in order. The server seed is committed by hash before you set a client seed, so neither side can steer a result — read more on how seeds work.
Frequently asked
How is a Stake Dice result generated?
roll = floor(float × 10001) / 100 — uniform from 0.00 to 100.00 in 0.01 steps. Win chance = target (under) or 100 − target (over). Payout = 99 / chance, i.e. a 1% house edge on every roll.
What do I enter to verify a Dice bet?
The revealed server seed, your client seed, the bet's nonce, and the options you played with. One float per bet: the first 4 bytes of HMAC-SHA256(server seed, client:nonce:0). Multiply by 10001, floor, divide by 100. "Roll under 49.50" wins when the number is below 49.50.
Where do I find the server seed, client seed and nonce?
On Stake: Fairness (the shield icon) → Seeds. The active server seed is only shown as a hash; rotate the pair and the previous server seed is revealed in plain text. The client seed is yours (Stake generates one or you type it). The nonce is the bet number within that seed pair — every bet's detail popup shows it.
Does anything I paste leave my browser?
No. The HMAC-SHA256 is computed by your browser's WebCrypto API; this page makes no network requests with your seeds and has no analytics on the inputs.
Can this predict the next roll?
No — and nothing can. The next roll needs the unhashed server seed, which Stake only reveals after you rotate away from it. Anyone selling a predictor for Stake is running a scam. What you can do is verify every past roll, which is what this tool is for.
What if the result doesn't match Stake?
Check the three inputs first: the revealed (unhashed) server seed, the exact client seed active at the time, and the right nonce. If they are right and it still doesn't match, you have a reproducible discrepancy — keep the bet ID and seeds and raise it with Stake support.
Other games
The DiceStrats extension runs creator strategies on your own Stake account, with take-profit and stop-loss armed by default and a ⚙ Seeds panel that rotates to a client seed you choose. Free with promo code DICESTRATS.