Stake.us Dragon Tower Verifier

Recompute the safe tiles on every level of the tower 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

Difficulty

Recomputes as you type. Nothing leaves your browser.

Dragon Tower Result

Paste the server seed and client seed from the bet. The dragon tower 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 Dragon Tower result

From float to result

Nine levels. On each level the operator draws the egg positions with a Fisher-Yates shuffle over that difficulty's tile count: easy places 3 eggs on 4 tiles, medium 2 on 3, hard 1 on 2, expert 1 on 3, master 1 on 4. Floats are consumed level by level.

What to compare

Pick the difficulty you played, then compare each level's eggs with the tower revealed in your bet history.

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 Crash verifier Stake.us Mines verifier Stake.us Flip verifier Stake.us Plinko verifier Stake.us Hilo verifier Stake.us Keno verifier Stake.us Wheel verifier Stake.us Diamonds verifier Stake Dragon Tower verifier Shuffle verifier Winna Dragon Tower 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 the difficulty change the layout?

It changes how many floats each level consumes (the egg count) and the tile count they are drawn from, so a different difficulty is a different reading of the same float stream.

Are the upper levels decided before I start climbing?

Yes. All nine levels are derived at bet time from the seeds and nonce.

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 eggs on every level.

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.