Stake Wheel Verifier
Recompute the landing segment and its multiplier on Stake from the server seed, client seed and nonce. Same HMAC-SHA256 stream the operator publishes, run in your browser.
Verification Inputs
Recomputes as you type. Nothing leaves your browser.
Wheel Result
Paste the server seed and client seed from the bet. The wheel result appears here as you type.
Read from the Wayback snapshot of 2025-07-19 (the live page challenges non-browser fetches); saved at research/casinos/stake/evidence/provably-fair-game-events-wayback-20250719.txt. Crash is verified on its per-seed curve only: live multiplayer Crash rounds come from a public hash chain, not your seed pair.
How Stake derives a Wheel result
From float to result
What to compare
Where the seeds are
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 orderOther Stake games
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.
Frequently Asked Questions
Why does the multiplier depend on the risk level?
The wheel is the same; the payout table under each segment changes with risk. Each published table averages 0.99 per spin.
What if my wheel has a segment count that is not listed?
Then this page shows the segment only. It never invents a multiplier for a table the operator has not published.
Which Stake algorithm does this use?
Stake, Provably Fair: Game Events, read 2026-09-20. The byte stream is HMAC-SHA256 of clientSeed:nonce:round keyed by the server seed, converted to 4-byte floats, then mapped to the landing segment and 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.
