How to Verify Any Stake.com Result: Step-by-Step

Published 2026-04-22 · Tags: guides, verifier

Rotate your server seed, grab three values, paste them into our verifier. Audit any bet outcome in 60 seconds.

Stake.com's provably fair system lets anyone, not just sophisticated users, confirm that any bet they've placed was decided by honest math. The process takes about 60 seconds per bet, or a minute total to audit an entire session. Here's exactly how to do it.

This guide assumes you understand why provably fair works. If you don't, read How Provably Fair Works first (it's short).

What you need

You need three things from Stake:

1. The old server seed (revealed after you rotate it)
2. Your client seed — the string your browser used
3. The nonces of the bets you want to verify (each bet uses a unique nonce, starting at 0 and incrementing by 1)

You also need our free Stake Verifier, or the Stake docs if you want to do the math by hand in a programming language. The verifier runs everything locally in your browser, so no data leaves your machine.

Step 1, Rotate your server seed

Log into Stake, open any game (Dice is fastest), and click the hashburger menu that shows your seeds. You'll see a section called "Fairness" or "Seeds" with three rows:

• Client seed (editable)
• Server seed (next) — hashed only, not yet active
• Active server seed, hashed

Click the button that says "Rotate server seed" or "Change seed pair". This does two things:

• Reveals the current active server seed (shows the full unhashed string)
• Swaps in the new server seed (which becomes active)

Important: you must rotate the seed before you can verify bets played with it. Active seeds are always hidden. Stake only reveals a seed once it's no longer being used, otherwise the casino's own bets would be predictable.

Step 2 — Copy the three values

Grab:

• The revealed (old) server seed, long hex or alphanumeric string, ~64 chars
• The client seed that was active, shorter, editable
• The nonce range you want to check — e.g. 0–250 if you played 251 bets in that session

Also note the game you played. Different games apply different math to the same HMAC output (Dice maps to 0–100, Limbo to a multiplier, Mines to a grid, etc.).

Step 3, Open the verifier

Go to StakeCruncher's verifier. It runs HMAC-SHA256 in your browser using standard crypto libraries. Nothing is uploaded. Nothing is logged.

Pick your game, paste the three values, and hit Verify.

Step 4, Compare to what Stake actually paid

The verifier shows the computed outcome for each nonce. For Dice, it's a number 0.00–99.99. For Limbo, it's a crash multiplier. For Mines, it's the hidden mine positions. For Crash, it's the bust point.

Go to your Stake bet history (Transactions → Bet Archive) and compare each bet's actual result to what the verifier calculated for the same nonce.

Every single one should match exactly. If even one is off, something's wrong and you've got proof.

Step 5 — Verify the hash chain (optional but bulletproof)

The strongest check: hash the revealed server seed yourself with SHA-256 and confirm it matches the hashed server seed Stake showed you when the session started.

Every Stake game interface shows the "Active server seed (hashed)" in advance. If you saved that hash, now compare:

SHA256(revealed_server_seed) === hash_shown_at_session_start ?

If yes → Stake committed to this exact seed before you bet. They couldn't have swapped it mid-session. If no → they changed the seed, which is a smoking gun.

In practice this check never fails for Stake (it'd be a career-ending scandal for the operator), but the point is you can check it. No other casino type, not live dealer, not non-provably-fair slots, lets you audit like this.

Common stumbling blocks

• "The seed I pasted isn't being accepted" — make sure you're using the revealed (unhashed) server seed. If you're copying a hash, verification can't work because hashing is one-way.
• "My nonces don't match Stake's bet IDs", nonces are per-seed-pair and start at 0 each time you rotate. Stake's bet IDs are global. They're not the same number.
• "The outcome doesn't match for one bet", double-check you have the right game selected. Dice uses different mapping from Limbo which is different from Mines. Also confirm the server seed wasn't already partially rotated during your session.
• "I don't want to rotate because I'm on a hot streak" — perfectly fine. Rotate at the end of your session. Nothing forces you to verify in real time.

How often should you actually verify?

Honestly? Once, when you're new to crypto casinos and want to confirm the math works. Then occasionally, maybe once a month, as a sanity check.

The point of provably fair isn't that you personally verify every bet. It's that anyone can verify any bet, and in practice some people do, and they'd scream instantly if something was off. That social accountability is the real guarantee. Your 60-second verification adds a data point to the pile.

Bulk verify an entire session

We're planning to add a "bulk verify" mode to the verifier where you paste a seed pair + a CSV of nonces and it checks all of them at once. If you'd find that useful, drop a note in our Telegram.

In the meantime, the single-bet verifier is plenty for spot-checks: try it now →