Server Seed vs Client Seed

Server seed and client seed are the two cryptographic inputs that a provably fair casino combines with a nonce to produce a verifiable game outcome.

What it means in practice

Server seed vs client seed describes the two secret inputs that sit behind every provably fair game outcome. The server seed is generated and hashed by the operator and kept secret until reveal, while the client seed is supplied or edited by the player. A round counter called a nonce increments with each bet, so the same seed pair can deterministically produce a long series of outcomes.

When a player places a bet, the casino hashes the combined server seed, client seed and nonce to derive a result, such as a crypto dice roll or a card draw. Because only the hash of the server seed is published up front, the operator cannot change the seed after seeing the player input, and the player cannot predict the result in advance. This commit-and-reveal structure is what distinguishes provably fair from a conventional RNG that players cannot inspect directly.

After the operator rotates the seed pair and reveals the raw server seed, the player can recompute every outcome and confirm nothing was tampered with. The two seeds protect against different attacks: the server seed stops the operator from cherry-picking results, while the editable client seed stops the operator from tailoring a seed to a known input. For a fuller contrast with certified randomness, see provably fair vs RNG.

Server Seed vs Client Seed

Side-by-side breakdown of how these two models compare across key dimensions.

Dimension
Server Seed
Client Seed
Who controls it
Generated by the operator/server.
Supplied or editable by the player.
Secrecy and reveal timing
Kept secret (only its hash is shown) until the round or session is closed, then revealed.
Visible to the player from the start and can be changed at will.
Role in verification
Proves the operator committed to a result before the bet.
Proves the player influenced the input the operator could not predict.
What it protects against
Operator pre-computing or cherry-picking favourable outcomes.
Operator choosing a server seed tailored to a known client input.
Player editability
Not editable by the player; rotated via a new seed pair.
Editable any time, which also rotates the verification chain.
Typical lifecycle
Hashed at commit, used across many nonces, revealed at rotation.
Persists until the player changes it, then a fresh pair begins.
Server Seed

Advantages

  • Forces a pre-commitment the operator cannot alter after the fact.
  • Hash publication gives a tamper-evident record.
  • Rotation lets players audit a whole batch of past rounds.

Limitations

  • Players must trust the hash until the reveal happens.
  • Outcome fairness still depends on the underlying game maths.
  • Useless if the operator never actually reveals the raw seed.
Client Seed

Advantages

  • Gives the player direct, ongoing control over an input.
  • Editable at any moment to reset the verification chain.
  • Removes the worry that the operator predicted the player input.

Limitations

  • Does nothing on its own without a committed server seed.
  • Many players leave the default value and never change it.
  • Editing mid-session can confuse less technical players.

When to choose which

Choose Server Seed

Reference the server seed when explaining how the operator pre-commits to a result and why the hash matters before a bet is placed.

Choose Client Seed

Reference the client seed when explaining how a player injects unpredictability and can independently reset the verification chain.

How Server Seed vs Client Seed works across industries

See how server seed vs client seed is applied in the verticals Track360 supports, from qualification logic and payout structure to the operational context behind each model.

Online Casino

Server Seed vs Client Seed in Online Casino

Online casino operators that run [provably fair](/glossary/provably-fair) titles expose the seed pair in the game UI so players can audit results. Affiliates promoting these brands can explain the server and client seed roles as a trust signal, while reminding readers that seed verification proves randomness, not a favourable [house edge](/glossary/house-edge).
Read More
iGaming

Server Seed vs Client Seed in iGaming affiliate programs

Across the wider iGaming stack, the seed-pair model mostly appears in crypto-native instant games rather than certified slots audited under traditional [RNG](/glossary/rng) testing. Operators should be clear in help content about reveal timing so support teams can answer fairness queries without overstating what the seeds guarantee.
Read More

How Track360 handles this

Track360 helps crypto casino operators measure how transparency features influence affiliate-referred player behaviour, tracking deposits and retention across provably fair titles so teams can see whether seed verification correlates with longer player lifetimes.

FAQ

Frequently Asked Questions

Common questions about server seed vs client seed, how it works in affiliate programs, and where it shows up across Track360's supported verticals.

A server seed is generated and hashed by the operator and kept secret until reveal, while a client seed is supplied or edited by the player. Combining both with a nonce produces each provably fair outcome, so neither side can manipulate the result alone.