What is a client seed in plinko?
It is the piece of the random recipe that belongs to you. Every drop is derived from three inputs, the casino's server seed, your client seed, and a bet counter, and the client seed is the only one under player control.
Provably fair systems are built on a simple standoff: neither party should be able to dictate results alone. The server seed covers the casino's side and is committed by hash before play. Your client seed completes the pair. Change it to any value you like and every future result under that pair shifts unpredictably, for both you and the house.
Where does the client seed enter the calculation?
Each drop computes HMAC-SHA256(serverSeed, clientSeed:nonce:cursor). The server seed acts as the key; your client seed leads the message, joined by the nonce and cursor. Altering one character of it produces a completely different digest and path.
Concretely, a client seed of my-lucky-cat at nonce 41 hashes the message my-lucky-cat:41:0. The resulting bytes become floats, one per row, and floor(float x 2) steers the ball left or right at each peg. Because HMAC-SHA256 has avalanche behavior, my-lucky-cat2 yields an unrelated 16-bounce path. You can replay this exact pipeline in our provably fair verifier.
Should you change your client seed, and when?
Set your own value at least once, since a self-chosen seed is the whole point of the mechanism. Changing it before each server seed rotation is good hygiene. It will not improve your odds; it preserves your proof of fairness.
Be clear about what the knob does. No client seed is luckier than another, and cycling seeds mid-session does nothing to the 1% house edge. What a fresh, self-typed seed guarantees is that the drops you later verify were provably outside the operator's sole control, which is the entire value of the system.
Test your own seed right now
Type any client seed into our verifier with a revealed server seed and nonce and watch the exact peg path it produces.
Open the Provably Fair Verifier