Stake Wheel Verifier
Verify the fairness of your Stake.com and Stake.us Wheel game winning segments using cryptographic proof
Understanding Stake Wheel
Game Statistics
How It Works
floor(float × segments) = winning segment100% Private
All verification happens entirely in your browser. Your seeds and bet data never leave your device.
How to Verify Stake Wheel Results
Step 1: Get your seed data from Stake
To verify a Wheel bet, you need three pieces of data plus the segment count:
- Server Seed (Unhashed): Go to Settings → Fairness on Stake. Click "Unhash" to reveal it.
- Client Seed: Found in the same Fairness settings page.
- Nonce: Find it in your bet history by clicking on the bet.
- Number of Segments: Note the wheel configuration (10, 20, 30, 40, or 50).
Note: You can only verify bets made before you unhash the server seed.
Step 2: Enter your data in the form above
Paste your data into the verification form:
- Enter your Client Seed exactly as shown on Stake
- Enter the Server Seed (Unhashed)
- Enter the Nonce for the specific bet
- Select the correct Number of Segments
Step 3: Compare the result with your bet
After clicking Verify, compare the winning segment (0 to N-1) with your actual game outcome.
If results don't match, double-check you're using the correct segment count and unhashed server seed.
Frequently Asked Questions
How does Stake Wheel work?
Stake Wheel lets you spin a wheel with 10, 20, 30, 40, or 50 segments. Each segment has a multiplier based on the risk level. The wheel spins and lands on a random segment. Higher segment counts with high risk offer bigger potential multipliers but lower odds. The game has a 99% RTP.
Does this verifier work for both Stake.com and Stake.us?
Yes! Both platforms use identical provably fair algorithms for Wheel.
How is the winning segment determined?
The HMAC-SHA256 algorithm generates a float value between 0 and 1. This float is multiplied by the number of segments and floored to get the winning segment (0 to N-1).
Is my bet data safe?
Absolutely. All verification happens 100% client-side in your browser. Your data never leaves your device.