Recompute any Stake-style result yourself — tested bit-for-bit against Stake.us' own calculator. Dice, Limbo, Plinko, Mines, Keno.
This tool computes everything locally via the Web Crypto API (HMAC-SHA256). Your server seed, client seed and nonce are never sent anywhere — the only network request is an anonymous, cookieless page-view counter (page path + referring page, nothing you type). View the math · it's the same code we test against Stake's own calculator.
Prefer a single-game page with the exact formula spelled out? Open the one you need:
Dice verifier · Limbo verifier · Plinko verifier · Mines verifier · Keno verifier
Before a bet, the casino shows you a hashed server seed (a commitment it can't change later). Your bet also uses your own client seed and an incrementing nonce. The result comes from:
HMAC-SHA256( key = server_seed , message = "client_seed:nonce:round" )That 32-byte digest is sliced into numbers in [0,1) and mapped to the game outcome. Once the casino reveals the server seed, you can recompute every past round exactly — which is what this tool does. If the recomputed result matches what the game showed, that round was honest.
These are the mappings we checked bit-for-bit against Stake.us' own /provably-fair/calculation page (Dice roll, Limbo value, Mines draw order, Keno numbers, Plinko left/right directions).
| Game | Floats | Mapping |
|---|---|---|
| Dice | 1 | floor(f · 10001) / 100 → 0.00–100.00 |
| Limbo | 1 | 16777216 / (floor(f · 16777216) + 1) · 0.99 → crash multiplier (2²⁴-based, as in Stake's live calculator — not the 1e8 formula from older docs) |
| Plinko | rows (8–16) | each float → Left/Right, bucket = number of Rights |
| Mines | = mines | sequential draw without replacement from 25 tiles (draw order) |
| Keno | 10 | draw 10 without replacement from pool 1–40 |
⚠️ For Plinko and Mines, set the row/mine count to exactly what the round used — a different setting gives a different (but still correct) result.
We have tested this verifier against Stake / Stake.us only. Other casinos that say they use Stake's algorithm (HMAC-SHA256 of client_seed:nonce:round, same game mappings) should give identical results — but we have not checked them, and some casinos use different formulas for some games. Before trusting a mismatch elsewhere, test one round you know the answer to. Crash in house-seed mode (a public seed chain instead of your client seed) works differently — see our dedicated Blaze Crash verifier and Aviator verifier.
Yes. The calculation runs entirely in your browser using the Web Crypto API. Your seeds are not sent to any server, logged, or stored (the page only counts anonymous page views — path and referring page, nothing you type). Once the page has loaded you can disconnect from the internet and it still works — and you can read the source of this page to confirm it.
No — and be very suspicious of anyone who claims to. While the server seed is still hashed (unrevealed), nothing can be predicted. This tool only checks past rounds after the seed is revealed. Any "predictor" that promises the next multiplier is a scam.
It means that single round was generated honestly from the committed seeds — the casino didn't tamper with that specific outcome. It does not tell you the house edge or whether the game is a good deal. Fair ≠ cheap. Our audits cover the house edge separately.
Only if that casino uses exactly Stake's algorithm (same HMAC message format and the same game mappings). Many Stake-style casinos say they do, but we have only tested Stake / Stake.us. Check one round you already know before relying on it elsewhere.
First check the obvious: the server seed must be the revealed/unhashed value, the nonce must match, and for Plinko/Mines the row/mine count must be exactly what the round used. A stray space or line break in a pasted seed is the most common cause (the verifier warns you when it removed one). If it still won't reconcile with correct inputs, that's exactly the kind of case worth reporting — see our methodology.
Formulas checked bit-for-bit against Stake.us' own calculator (Aug 2026). Other casinos not tested. Open methodology: /methodology/. © FairPlay Audit — independent, free and open source (MIT).