Stake.us Crash Verifier

Recompute the crash point your seed pair would produce on Stake.us from the server seed, client seed and nonce. Same HMAC-SHA256 stream the operator publishes, run in your browser.

Verify one betAnalyze a range

Casino

Game

Have a bet link? paste it; we open the right casino and game and tell you where the seeds are. Nothing is sent anywhere.

Examples

Verification Inputs

Server Seed unhashed, revealed after you rotate

Client Seed your chosen seed

Nonce bet counter, starts at 0

Server Seed Hash optional, the SHA-256 shown before you bet

Recomputes as you type. Nothing leaves your browser.

Crash Result

Paste the server seed and client seed from the bet. The crash result appears here as you type.

Algorithm sourceStake.us, Provably Fair: Game Events (identical scheme to Stake.com)checked 2026-08-17

The byteGenerator, float conversion and every per-game event mapping were confirmed identical to Stake.com (14 of 14 claims, research/platform/tools/tool-finesse-audit/STAKE_COM_VS_US_2026-08-17.md). Roulette is not in that confirmation set, so it has no Stake.us route yet.

Stake.us fairness page Stake.us on GAMB·8

How Stake.us derives a Crash result

From float to result

This uses the same curve as Limbo on your seed pair. Live multiplayer Crash rounds are seeded from a public hash chain and a salt, not from an individual player's seeds, so this page verifies the per-seed math and cannot reproduce a specific live round.

What to compare

Use this to confirm the conversion. To verify a live round, use the operator's hash-chain verifier with the round hash from the bet.

Where the seeds are

Open the bet in your history on Stake.us. The client seed and nonce show immediately. The unhashed server seed appears only after you rotate your seed pair, so rotate first, then verify every bet from the old pair.

The byte stream, Stake.us

bytes = HMAC_SHA256(key = serverSeed, msg = clientSeed:nonce:round) // round starts at 0float = b0/256 + b1/256^2 + b2/256^3 + b3/256^4 // 4 bytes per floatresult = game event mapping applied to the floats, in order

Other Stake.us games

Stake.us Dice verifier Stake.us Limbo verifier Stake.us Mines verifier Stake.us Flip verifier Stake.us Plinko verifier Stake.us Hilo verifier Stake.us Keno verifier Stake.us Dragon Tower verifier Stake.us Wheel verifier Stake.us Diamonds verifier Stake Crash verifier Shuffle verifier Winna verifier

Keep what you worked out.

A free account saves your bankroll plans, sessions and the results you run here, on every device. No card, no upsell.

Create free account All tools

Frequently Asked Questions

Why does my live Crash round not match?

Because live Crash is a shared round. Its multiplier comes from a pre-committed hash chain published on BitcoinTalk, not from your server seed, client seed and nonce.

What does this page verify, then?

The seed-to-multiplier conversion itself, and any single-player game that uses it. It is the same code path as Limbo.

Which Stake.us algorithm does this use?

Stake.us, Provably Fair: Game Events (identical scheme to Stake.com), read 2026-08-17. The byte stream is HMAC-SHA256 of clientSeed:nonce:round keyed by the server seed, converted to 4-byte floats, then mapped to the per-seed crash multiplier.

Do my seeds leave the browser?

No. The HMAC and SHA-256 run with the Web Crypto API on your device. The share link carries the seeds only because you copied it.