Verify a Stake bet
A Stake bet verifier needs three values: the revealed server seed, your client seed and the bet's nonce. Paste them below and this page recomputes the result in your browser, exactly as Stake does, for Dice, Limbo, Plinko, Mines, Keno, Roulette and Crash. Add the server seed hash that was shown before play and the commitment is checked too. With the example pair at nonce 7, the Dice roll is 50.57; press “Load example values” to see the working.
Disclosure: VerifyRoll is sponsored by Craze, a competitor of Stake. Figures here are computed or taken from what operators publish, dated; nothing is estimated.
Loading verifier…
Where to find the seeds on Stake
- Open the bet. Open the bet in your Stake history and find its Fairness (sometimes Verify) panel. It shows three things: the server seed hash, your client seed and the bet's nonce.
- Rotate the seed pair. A server seed is revealed only after it is retired. Rotate your seed pair; the previous server seed is then shown in plain text. Every bet made under it can now be checked. Bets under the new, still-hidden seed cannot be checked yet, by design.
- Copy four values. Copy the revealed server seed, the server seed hash that was shown before play, your client seed and the nonce of the bet you want to check. The nonce goes up by one with every bet made under the same seed pair, so it identifies the bet.
- Paste and verify. Paste them into the verifier above with the game selected. VerifyRoll first checks SHA-256(server seed) against the hash, then recomputes HMAC-SHA256(server seed, "clientSeed:nonce:cursor") and maps the floats through the game's formula. Compare the result with what Stake showed you.
Crash is different: no seed pair
- Find the game hash. Each Crash round on Stake has a game hash from a pre-committed chain. It is published with the round's fairness details once the round has ended; the chain is played backwards, so revealing it cannot affect later rounds.
- Find the public client seed. The public client seed is a Bitcoin block hash the operator chose after publishing the chain. It is the same for every round and is stated on the operator's Crash fairness page.
- Paste and verify. Select Crash, paste the game hash and the public seed. VerifyRoll computes HMAC-SHA256(game hash, public seed), reads the first 52 bits and applies max(1, floor(99 ÷ (1 − X)) ÷ 100). Compare with the crash point shown.
Which Stake games verify here
All seven Originals below. Each link opens the verifier preselected for that game, with the derivation, the RTP Stake publishes and a worked example.
| Game | Inputs | Floats used | Published RTP |
|---|---|---|---|
| Stake Dice verifier | server seed, client seed, nonce | one float | 99% |
| Stake Limbo verifier | server seed, client seed, nonce | one float | 99% |
| Stake Plinko verifier | server seed, client seed, nonce | one float per row (8, 12 or 16) | 99% |
| Stake Mines verifier | server seed, client seed, nonce | one float per mine | 99% |
| Stake Crash verifier | game hash + public seed | one 52-bit value per round (not a seed-pair float) | 99% |
| Stake Keno verifier | server seed, client seed, nonce | ten floats | 99% |
| Stake Roulette verifier | server seed, client seed, nonce | one float | 97.3% |
RTP as published by Stake, checked 2026-09-23. The figure in the game's own info panel wins.
Example: one Stake Dice roll, worked
Computed on the server by the same function the verifier runs, from the example seed pair at nonce 7. These are not seeds from a real Stake round.
inputsStake scheme
- server seed
- 2b4d2f1a7c9e0f3b8a6d5c4e3f2a1b0c9d8e7f6a5b4c3d2e1f0a9b8c7d6e5f4a
- client seed
- verifyroll
- nonce
- 7
derivationdice
- HMAC-SHA256(server seed, “verifyroll:7:0”)81727d41db6b44706ddfd681ab9cd0124cc482392adbbdda8ac8ac626566bf1a
- float = 0.5056532176677138
- roll = floor(float × 10001) / 100 = 50.57
Questions
- Is Stake provably fair?
- Stake publishes the HMAC-SHA256 seed-pair scheme this verifier implements, so every bet under a revealed server seed can be recomputed here. "Provably fair" proves the result was fixed before you bet and not changed afterwards; it says nothing about the odds. Those are the published RTP figures: Dice 99%, Limbo 99%, Plinko 99%, Mines 99%, Crash 99%, Keno 99%, Roulette 97.3% (checked 2026-09-23).
- Why can't I verify the Stake bet I just made?
- Because its server seed is still hidden. The operator shows only SHA-256 of the seed while it is in use, which is what stops it changing the seed later. Rotate the pair, and the seed you were playing under is revealed; then every bet made under it verifies.
- Which Stake games can VerifyRoll recompute?
- Dice, Limbo, Plinko, Mines, Crash, Keno, Roulette. Six use the seed pair and the nonce; Crash uses a game hash from a pre-committed chain and the public client seed. Each has its own page with the derivation and a worked example.
- Does VerifyRoll send my seeds anywhere?
- No. The hashing runs on the WebCrypto API in your browser, and the site's content-security policy allows connections to itself only. You can verify with the network disconnected once the page has loaded.
Next
- Stake in the casino directory: support status, scheme and every published RTP figure
- Game maths: how each Original derives its result under this scheme
- Verify a Shuffle bet: same construction, separate operator
- How provably fair works: what a passing check proves and what it does not
last reviewed 2026-09-27