BC.Game Wheel Verifier
Verify the fairness of your BC.Game Wheel spin outcomes using cryptographic proof
Understanding BC.Game Wheel
Game Statistics
How It Works
floor(float × segments), counted from 0
100% Private
All verification happens entirely in your browser. Your seeds and bet data never leave your device - we don't collect, store, or transmit any information.
How to Verify BC.Game Wheel Results
Step 1: Get your seed data from BC.Game
To verify a Wheel bet, you need three pieces of data plus the segment count and risk level:
- Server Seed (Unhashed): Go to Settings → Fairness on BC.Game. Click "Unhash" or reveal your active server seed.
- Client Seed: Found in the same Fairness settings page. You can use BC.Game's default or set your own.
- Nonce: Each bet has a unique nonce. Find it in your bet history by clicking on the bet details.
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 BC.Game
- Enter the Server Seed (Unhashed) - this is the revealed seed, not the hash
- Enter the Nonce for the specific bet you want to verify
- Set the Number of Segments (default is 50) and the Risk Level (default is Low) to match your spin
The verifier calculates the result using BC.Game's exact HMAC-SHA256 algorithm.
Step 3: Compare the result with your bet
After clicking Verify, you'll see the calculated wheel segment:
- The result will be the landed segment and the payout at that position in BC.Game's table for your segments and risk level
- Compare this with the wheel segment shown in your BC.Game bet history
- If they match exactly, the bet was provably fair
If results don't match, double-check you're using the unhashed server seed, correct nonce, and matching segment count and risk level.
Frequently Asked Questions
How does BC.Game Wheel determine the winning segment?
BC.Game Wheel uses HMAC-SHA256 cryptographic hashing to generate a provably fair result. The algorithm combines your server seed, client seed, and nonce to create a hash. Its first 4 bytes become a float between 0 and 1, which BC.Game's own verifier takes to 9 decimals, multiplies by the number of segments and rounds down: that is the landed segment, counted from 0. It pays the multiplier at that position in BC.Game's Wheel table for your segments and risk level, which returns 98%.
What is the number of segments field for?
The number of segments represents how many sections the wheel is divided into. BC.Game Wheel comes in 10, 20, 30, 40 or 50 segments, and this verifier starts at 50. Make sure to enter the same number of segments as shown on the wheel you played to get accurate verification results.
Why doesn't my verification result match?
Common reasons for mismatched results:
- Using hashed server seed: You need the unhashed (revealed) server seed, not the hashed version.
- Wrong nonce: Each bet has a unique nonce - verify you're using the exact nonce for that bet.
- Incorrect segment count: Make sure the segment number matches the wheel configuration you played.
- Seed pair mismatch: The seeds must be the pair that was active when the bet was placed.
Is my bet data safe when using this tool?
Absolutely. All verification happens 100% client-side in your browser using JavaScript. Your seeds, nonces, and bet data never leave your device - we don't collect, store, or transmit any information to our servers.