What is a nonce in plinko?
A nonce, "number used once," is the bet index attached to each drop. Your first bet under a seed pair carries nonce 0, the next nonce 1, and so on, giving every wager its own distinct random result.
The server seed and client seed typically stay fixed for hundreds of bets, so something must distinguish drop number 7 from drop number 300. That something is the nonce. It is not secret and not random; it is an honest public counter that both you and the casino can read at any time in the fairness panel.
Why does every drop need its own nonce?
Because HMAC is deterministic. HMAC-SHA256(serverSeed, clientSeed:nonce:cursor) always returns the same digest for identical inputs, so without an incrementing nonce every drop would repeat one outcome forever. Changing the counter changes the message, which changes everything.
The message for your fifth bet under seed pair X might read myseed:4:0; the sixth reads myseed:5:0. One digit moved, yet SHA-256's avalanche effect makes the two digests unrelated, sending the ball down entirely different peg paths. Determinism plus a counter is what lets a fixed seed pair serve a whole session while staying fully provably fair.
How do you use the nonce when verifying a drop?
Find the bet in your history, note its nonce, and after the server seed is revealed feed both seeds plus that nonce into a verifier. It recomputes that exact drop's path and bin, which must match your recorded result.
The counter is your lookup index into the whole session: nonce 250 always regenerates your 251st bet, no matter when you check it. Paste the values into our provably fair verifier for the replay, or flip the plinko simulator into provably fair mode and step the nonce forward yourself to preview how one counter tick reshapes the path.
Step through nonces yourself
Switch the simulator into provably fair mode, fix a seed pair, and advance the nonce one bet at a time to watch each unique path.
Open the Plinko Simulator