On this page
What provably fair means
A hash published before your bet ties the game to the secret it will reveal later. Once that secret is available, you can reproduce the commitment and the result without relying on the animation.
That gives you an individual round to verify. Keeping the original hash matters because it is the value the revealed secret must match.
Hash before
Keep the commitment shown before betting. The secret stays hidden while the seed pair is active.
You play
Your client seed joins the server seed in the result calculation. The bet number identifies the drop.
Secret after
100HP reveals the server seed when you rotate the seed pair in the Seeds tab.
You check
Hash the revealed seed, compare the commitment, then reproduce the ball’s path with the recorded inputs.
At 100HP, rotating the pair also activates the next server seed and resets the bet count. Retain the inputs for the old pair to reproduce its drops after rotation.
Seeds, nonce and cursor: the inputs
100HP combines a hidden server seed with your client seed, while the nonce changes with each bet. The cursor supplies more random bytes when a drop needs them.
A server-generated secret whose SHA-256 hash is visible before betting.
plinko-ing-clientYour part of the calculation; this is the value used in the worked drop.
The bet number for the current pair, increasing by one with each bet.
The counter that advances for the next block of random bytes.
Changing your seed changes the stream of results; the multiplier table and the RTP stay the same, which is why seed changes are not a strategy.
Recompute a drop: the 100HP algorithm
100HP needs two HMAC calls for a full-length ball path, with each row taking its own number. Its Provably Fair panel publishes the conversion, allowing the landing bin to be reproduced from the revealed inputs.
HMAC-SHA256 uses the server seed as its key and clientSeed:nonce:cursor as its message. Each group of four bytes becomes a number through b0/256 + b1/256² + b2/256³ + b3/256⁴; floor(number × 2) gives a left turn for zero or a right turn for one, and the right-turn count gives the bin.
100HP worked drop: example seeds written for this page, not a casino’s seed.
| Step | What happens | Value in our example |
|---|---|---|
| Server seed | HMAC key; hidden until reveal | 3331b0b32ea27f77adc9a0d5e5f9709d5a45c843f90b2a5c9266fdd5e13f444f |
| SHA-256 commitment | Hash of the server seed before betting | 61a9458ce949bb3c743881c8618454c722a08c93682a96ddd479b894c8ca8351 |
| Client seed | Player contribution | plinko-ing-client |
| Nonce | Bet number for this pair | 0 |
| HMAC cursor 0 | First block of bytes | 84a34b569c7ba85bb7dd1287f310ea5a72d029ec724e8639cb4bb475250868eb |
| HMAC cursor 1 | Next block of bytes | 972fa3a493120d56ad689201588768fcfeb9622b46fa30a791db35cabf1c2657 |
| 16 numbers | Read consecutive groups of bytes | 0.518117, 0.611262, 0.718217, 0.949477, 0.448489, 0.446511, 0.794124, 0.14466, 0.590571, 0.574494, 0.677377, 0.345816, 0.995016, 0.277255, 0.569751, 0.746523 |
| Path | Read from the top row | 1111 0010 1110 1011 |
| Bin | Right turns in the path | 11 |
| Multiplier | 100HP, 16-row table | Low 1.2× · Middle 2.3× · High 1.3× · Extreme 0.8× |
| Bin probability | Chance of this landing bin | 6.67% |
The same landing position pays differently across risk settings, so reproducing a path gives you the bin to compare with the selected table. All balls in a drop share the nonce: ball k starts at number 16k and consumes as many numbers as the board has rows.
The 100HP round hash contains 128 hexadecimal characters, with the result hidden before disclosure. Use the server-seed commitment for the SHA-256 comparison above.
What the match proves
The revealed seed matches the commitment, and the recorded inputs reproduce the displayed bin.
What it does not prove
A matching drop does not promise a profit or settle whether the casino will pay a withdrawal.
The distribution check
We ran 20,000 random seed pairs through the same calculation. The share of drops per bin follows the binomial chances of the classic board: C(16,k)/65,536 for bin k.
| Bin | Observed share | Theoretical chance |
|---|---|---|
| 4 | 2.71% | 2.78% |
| 6 | 12.1% | 12.2% |
| 8 | 19.5% | 19.6% |
| 10 | 12.4% | 12.2% |
| 12 | 2.9% | 2.78% |
| 16 | 0.01% | 1 in 65,536 |
Each outer bin has a theoretical chance of 1 in 65,536, so one of the two comes up once in 32,768 drops. The 100HP Plinko risk settings decide the multiplier attached to each landing position.
Why one letter matters
Changing the final letter of the example secret changes 122 of the hash’s 256 bits. That sensitivity makes the original commitment useful when you compare it with the revealed secret.
Illustrative secrets for the hash comparison.
| Example secret | SHA-256 |
|---|---|
plinko-ing-example-server-seed | a11c80671c73ae7e638f5d5cb80b84ca1e24ba92203d51c3cb7b3c5d1ff9c286 |
plinko-ing-example-server-seee | f4fdbf0347d38d70bf8e8920fb7fbe323e0a91743601d904c40e41f98d6a5c0c |
Which Plinko games are provably fair
Turbo Games uses a commit, play and reveal sequence; BGaming commits to Result plus Secret before applying the client seed. The game and studio determine which inputs you use for verification.
100HP exposes the path calculation above, while Stake provides a Fairness panel with Seeds and Verify. Spribe supports server and client seeds and lets you change the seed.
| Game | Studio | What you check with | Source |
|---|---|---|---|
| Plinko | 100HP Gaming | Server seed, client seed and nonce; reproduce the path | 100HP Provably Fair panel |
| Plinko | BGaming | SHA-256 of Result + Secret before betting; client seed; Result + Secret and Final Result after the round | BGaming |
| Plinko | Spribe | Server seed and client seed; change seed | SlotCatalog (catalogue) |
| Stake Plinko (Original) | Stake | Fairness → Seeds → Verify | Game Fairness panel |
| Plinko 3000 | Turbo Games | Commit → play → reveal; SHA-256 | Turbo Games |
| Turbo Plinko | Turbo Games | Commit → play → reveal; Hash, Salt, Server Seed, Client Seed, RNG version, Encrypted Hash | Turbo Games |
BGaming Plinko 2, XY and Easter use certified RNG, with laboratory certification and licensing providing the checks. The provably fair system for the original BGaming Plinko belongs to that game.
Provably fair, RTP and a tested generator
100HP’s declared RTP is 98%, while its seed calculation lets you reproduce an individual drop.
A laboratory test addresses the generator. Your own round verification addresses the commitment and the result you received.
Round was not changed
Provably fair verification lets you match the revealed secret and reproduce the outcome from the recorded inputs.
What the game returns
The paytable combines each landing probability with its multiplier to determine long-run RTP.
Generator was tested
Laboratory certification provides a test of the random-number generator used by the game.
Proves
- A matching commitment fixes the revealed secret.
- A matching calculation reproduces the round.
- A paytable calculation establishes the theoretical return.
Does not prove
- Round verification does not make the next drop predictable.
- RTP does not guarantee your session’s return.
- A generator certificate does not promise a withdrawal payment.
Your Plinko RTP comes from the table over the long run; a short session can finish above or below it.
Is Plinko rigged?
A drop that matches its commitment and recomputed bin has not been substituted after your bet. Provably fair gives you a repeatable calculation for that result.
A seed panel, a public RTP and a casino licence give you practical checks on the game and account. For certified RNG games, the laboratory certificate supplies the generator check.
The legitimacy of the casino and app determines where you play and which account protections apply.
Myths: seeds, predictors, bots
A changed seed changes the stream of numbers while leaving the paytable intact. A predictor cannot reconstruct the next bin from the commitment because the server seed remains hidden until disclosure.
| Claim | Consequence for the player |
|---|---|
| Change the seed to win | A new seed changes results, with the same multiplier table and RTP. |
| A predictor reads the next bin | The result depends on a server seed you do not know before reveal. |
| A bot or app supplies an edge | Automation does not reveal the secret; fake Plinko apps concern the software you trust with your account. |
Plinko strategy starts from rows, risk and stake; the client seed leaves the return in place.
Page history
- Added the 100HP seed-to-bin calculation, a worked drop, the distribution comparison and game verification systems.
18+ only. Some links on this page earn us a commission from the casino; it does not change the price for you.