Client Seed

In the provably fair roll function, the casino's server seed acts as the secret key and your client seed, joined with the nonce, forms the message: HMAC-SHA256(serverSeed, clientSeed:nonce). Change one character of the client seed and every subsequent roll in the sequence changes completely, thanks to the avalanche property of SHA-256.

Unlike the server seed, the client seed carries no secrecy requirement. Its power is not that it is hidden; it is that the house did not choose it and cannot predict it before committing to its own seed.

Order of operations is the entire argument. The commitment sequence runs:

1. The casino generates a server seed and publishes SHA-256(server seed).
2. You set a new client seed, any string you like.
3. Rolls begin, each one fixed by the now-locked seed pair and a rising nonce.

Because step 1 happens before step 2, a dishonest operator would need to pick a server seed that loses against every possible client seed, which is impossible since outcomes are uniformly distributed across inputs. Accepting the default client seed weakens this argument slightly: the site generated both values, so in theory it could have paired them. Typing even a short custom string after seeing the hash closes that gap completely. It costs five seconds and turns the fairness proof from probable to airtight.

Every serious dice site exposes the client seed in a fairness panel, usually one click from the game. The panel shows three values: the active client seed, the hashed server seed, and the current nonce. Editing the client seed typically starts a fresh seed pair with the nonce back at 0.

Practical habits worth adopting:

• Set a fresh custom client seed immediately after every rotation.
• Avoid meaningful personal strings; a random phrase works fine since the value is public anyway.
• Note the client seed, server seed hash, and date together so later verification is painless.

How prominently a casino surfaces these controls is a genuine quality signal. Our Stake dice review covers one of the cleaner implementations: seed pair, nonce, and rotation all live in a single dialog with full bet-level lookup.

Sellers of "winning seeds" exploit a misunderstanding of what the client seed does. HMAC-SHA256 output is computationally indistinguishable from uniform randomness for any input, so no seed is hot, cold, or due. A seed that just produced five wins has exactly the same distribution over its next roll as any other.

The client seed is a fairness instrument, not a strategy lever. Expected value is set entirely by the house edge, and no input string moves it. If someone claims otherwise, they are selling randomness with a story attached.