BC.Game Plinko Verifier
Verify the fairness of your BC.Game Plinko ball paths and landing positions using cryptographic proof
Understanding BC.Game Plinko
Game Statistics
How It Works
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 Plinko Results
Step 1: Get your seed data from BC.Game
To verify a Plinko bet, you need three pieces of data from BC.Game:
- Server Seed (Unhashed): Go to your BC.Game Fairness settings. Click "Unhash" or reveal your active server seed to get the unhashed version.
- Client Seed: Found in the same Fairness settings page. You can use BC.Game's default or set your own custom seed.
- Nonce: Each bet has a unique nonce number. Find it in your bet details or bet history.
Note: You can only verify bets made before you unhash the server seed.
Step 2: Enter your data in the form above
Fill in the verification form with your bet information:
- Enter your Client Seed exactly as shown on BC.Game
- Enter the Server Seed (Unhashed) - this is the revealed seed, not the hashed version
- Enter the Nonce for the specific bet you want to verify
- Select the Number of Rows you played with (8-16)
The verifier uses BC.Game's exact HMAC-SHA512 algorithm to calculate the ball path.
Step 3: Compare the result with your bet
After clicking Verify, you'll see the calculated ball path and landing position:
- The result shows the complete path with LEFT (L) and RIGHT (R) movements for each row
- The final landing position indicates which bucket the ball landed in
- Compare this with the ball path shown in your BC.Game bet history
If results don't match, verify you're using the unhashed server seed, correct nonce, and matching row count.
Frequently Asked Questions
What algorithm does BC.Game Plinko use?
BC.Game Plinko uses HMAC-SHA512 cryptographic hashing to generate provably fair ball paths. For each row, the algorithm takes 4 bytes from the hash, converts them to a float value between 0 and 1, then determines LEFT (≤0.5) or RIGHT (>0.5) movement. This creates a verifiable path from 8 to 16 rows.
How many rows can I verify in BC.Game Plinko?
BC.Game Plinko supports 8 to 16 rows. You must select the exact same number of rows that you played with when placing your bet. The row count affects the number of possible landing positions and the multiplier values for each bucket.
Why doesn't my BC.Game Plinko verification result match?
Common reasons for mismatched results:
- Using hashed server seed: You need the unhashed (revealed) server seed, not the hashed version shown initially.
- Wrong row count: Make sure you select the same number of rows (8-16) that you played with.
- Incorrect nonce: Each bet has a unique nonce - verify you're using the exact nonce for that specific bet.
- Seed pair mismatch: The seeds must be the pair that was active when the bet was placed.
Is my BC.Game bet data safe when using this verifier?
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. You can even disconnect from the internet after loading the page and the verifier will still work.
What's the difference between BC.Game Plinko and Stake Plinko?
BC.Game Plinko uses HMAC-SHA512 hashing and supports 8-16 rows, while Stake Plinko uses HMAC-SHA256 and typically supports 8-16 rows with different multiplier structures. Each platform has its own unique provably fair algorithm, so you must use the correct verifier for each casino.