Shuffle Plinko Verifier
Verify the fairness of your Shuffle.com and Shuffle.us Plinko game outcomes using cryptographic proof
Understanding Shuffle Plinko
Game Statistics
How It Works
clientSeed:nonce:round; each round gives 8 floats
floor(float × 2): 0 = Left (L), 1 = Right (R); the payout is the table entry for the number of rights
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 Shuffle Plinko Results
Step 1: Get your seed data from Shuffle
To verify a Plinko bet, you need the following data:
- Server Seed (Unhashed): Shuffle reveals it when you rotate your seed pair. Open the Plinko bet in your bet history, rotate the pair from its Provably Fair section, and the bet's details then show the unhashed server seed.
- Client Seed: Found in the same bet details under the Provably Fair section. You can use Shuffle's default or set your own custom seed.
- Nonce: Each bet has a unique nonce number. Find it in the bet details alongside the seeds.
Note: Shuffle reveals a server seed only when you rotate the seed pair; finishing a round does not reveal it. Every bet made on the old pair can then be verified.
Step 2: Enter your data in the form above
Paste your data into the verification form:
- Enter your Client Seed exactly as shown on Shuffle
- Enter the Server Seed (Unhashed) - this is the revealed seed, not the hash
- Enter the Nonce for the specific bet you want to verify
- Select the Risk (Low, Medium or High) and the Number of Rows (8 to 16) you played the bet with
The verifier calculates the result using Shuffle's exact HMAC-SHA256 algorithm.
Step 3: Compare the result with your bet
After clicking Verify, you'll see the calculated Plinko path, landing slot and payout:
- The path will be a sequence of L (left) and R (right) moves
- The landing slot will be a number from 0 (all left) to the number of rows (all right), with its payout from Shuffle's table for your rows and risk
- Compare the path, slot and payout with your Shuffle bet history
If results don't match, double-check you're using the unhashed server seed, correct nonce, and the bet's rows and risk.
Frequently Asked Questions
What are the Shuffle Plinko row options and how do they work?
Shuffle Plinko lets you pick any row count from 8 to 16 and a Low, Medium or High risk level (it starts on 8 rows, Medium). The ball drops from the top and goes left (L) or right (R) at each row. More rows mean more landing slots, and each rows and risk setting has its own payout table, from 5.6x at the edges (8 rows, Low) to 1,000x (16 rows, High); every table returns about 99%. The landing slot runs from 0 (all left) to the number of rows (all right).
Does this verifier work for both Shuffle.com and Shuffle.us?
Yes! Both Shuffle.com (international) and Shuffle.us (US version) use identical provably fair algorithms for Plinko. This verifier works for both platforms - just enter your seeds, nonce, rows and risk from either site.
What does the L/R path sequence mean?
The path sequence shows the exact route the ball takes as it drops through the pegs. Each letter represents a move at one row: L means the ball bounced left, R means it bounced right. For example, "LRLRLLRR" means the ball went left, right, left, right, left, left, right, right. The landing slot is the number of R (right) moves.
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 rows or risk: Make sure you select the same number of rows (8 to 16) and risk level you used in your actual bet.
- Wrong nonce: Each bet has a unique nonce - verify you're using the exact nonce for that bet.
- 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.