Server seed and client seed flow cover with three-seed verification visual

Server Seed and Client Seed: How Crash Game Randomness Actually Works

Server seed and client seed are the two halves of the cryptographic key that determines crash game outcomes. The server seed is generated by the casino before the round; the client seed comes from players. Neither party fully controls the result; the combination is what produces the cryptographic guarantee. Spribe's innovation was using THREE client seeds (from the first three players in each round) instead of one; the structural difference matters. This piece walks through the mechanics at the bit level.

Bit-level seed mechanics Reading time: 10 min Last updated

Key takeaways
  • Server seed: long random hexadecimal string (64 chars for SHA-256, 128 chars for SHA-512) generated by the casino's server before the round starts. Held privately on the server until after the round; the SHA hash of the seed is published before bets close.
  • Client seed: hex string contributed by players. Spribe (Aviator) pulls three client seeds from the first three players who place bets in each round. SmartSoft (JetX) uses one client seed from the bet-placing player. 1win Gaming (Lucky Jet) uses four (player + three live others). BGaming uses one client seed plus optional Bitcoin block hash for additional entropy.
  • The seeds combine via concatenation plus hash. Server seed + delimiter + client seed(s) + delimiter + nonce → SHA-256 or SHA-512 → hexadecimal digest. The first 13 hex characters of the digest (Spribe) or first 8 characters (most others) are converted to a fraction h between 0 and 1, which feeds the crash multiplier formula.
  • The reveal protocol guarantees verifiability. After the round ends, the casino publishes the original server seed in plaintext. Anyone can hash the revealed seed via the same SHA function and confirm it matches the pre-published hash. If they match, the seed was committed pre-round (binding); if they do not match, the casino changed the seed (which would be public evidence of cheating).
  • If an operator does not reveal seeds after the round, the game is not provably fair regardless of marketing. The reveal is what makes the cryptographic commitment meaningful; without it, you have only the casino's word about what seed was used. Refuse to play crash on operators that hide seed revelation. Tier 1 licensed operators always reveal; offshore Curacao operators sometimes hide.
128 hex
Server seed length (SHA-512)
3
Aviator client seeds per round
1
JetX client seeds per round
4
Lucky Jet client seeds per round

The two seeds that determine every crash round

Wondering what server seed and client seed actually do? They are the two inputs that determine every crash round outcome. The server seed is generated by the studio. The client seed is generated by the player (or by multiple players in Aviator). Together they hash to produce the crash point.

Bottom line

Server seed: long random hexadecimal string (64 chars for SHA-256, 128 chars for SHA-512) generated by the casino's server before the round starts. Held privately on the server until after the round; the SHA hash of the seed is published before bets close. Client seed: hex string contributed by players. Spribe (Aviator) pulls three client seeds from the first three players who place bets in each round. SmartSoft (JetX) uses one client seed from the bet-placing player. 1win Gaming (Lucky Jet) uses four client seeds for additional manipulation resistance.

The trick that makes this provably fair: the server seed is committed (hashed publicly) before the round starts, but only revealed after. The client seed is yours and you can change it. Neither side can manipulate the outcome unilaterally.

Why server seed has to commit first

Curious why timing matters? If the operator knew your client seed before they committed the server seed, they could pick a server seed that produces a low crash point. Bad outcome for you.

By committing first (publishing the SHA hash of the server seed), the operator locks in their input. They cannot change the server seed after seeing your client seed - the hash would not match the commitment, and you would catch them.

"Provably fair is not about trust. It is about commitment timing. The operator commits before they know your move. You commit after you see their hash. Neither side can cheat."
on why the seed commitment order is the entire trust mechanism

What client seed actually controls

Client seed is randomness you provide to the round. Most players use whatever the game generates by default. Some players manually rotate their client seed for each round to add personal entropy.

Important: the client seed does not affect your odds of winning. It is mathematically a randomization input, not a strategy input. Picking 12345 vs picking abc123 gives identical probability distributions.

The reason client seed exists: it prevents the operator from being able to predict the outcome. If they only used the server seed, they could compute every round in advance. Adding your client seed locks them out.

Three-seed and four-seed schemes

Aviator uses three client seeds pulled from three random players each round. Lucky Jet uses four. The math idea: more seed sources mean no single player (or the operator colluding with one player) can manipulate the round.

Practical effect: you cannot influence rounds you participate in beyond providing your own client seed. The other seeds come from random players you do not know.

How to actually rotate client seed

Most crash games let you set a custom client seed in settings. Pick anything - your favorite number, the time you logged in, a random string. Change it whenever you want.

Whether you change it or not, the game still works correctly. Rotation is for paranoid players who want maximum personal entropy. For most players, the default is fine.

What happens after the round

The operator reveals the server seed. You can verify the SHA hash matches the commitment from before the round. Then you compute the crash point yourself using all the seeds. If your computation matches the game's output, the round was honest.

That is the entire mechanism. Two seeds, two timing rules, one verification step. Nothing magical.

Read more: Provably fair guide, Verify any round, How the algorithm works.

For our test method, see the editorial policy.

Common questions readers ask

Is this strategy actually profitable? No crash strategy beats the locked house edge. The 3% edge on most aviation crash and the 1% on Cash or Crash Live applies regardless of cashout target. What strategies do is shape variance - whether you experience steady drains or occasional big wins on the way to the same expected outcome.

Should you trust the math? If the game is provably fair, yes. You can verify any round yourself with the seeds the operator reveals. We cover the verification process in our verification guide. If the game uses certified RNG instead (live formats), you trust GLI or iTech Labs auditing instead of self-verification.

How do you know whether the operator is honest? Check the license. UKGC, MGA, and NJDGE-licensed operators have regulatory consequences for cheating. Curacao-only operators have weaker enforcement but published audit reports if reputable. We always recommend verifying license status in the public registers before funding any operator account.

What is the difference between RTP and house edge? They are two sides of one coin. Subtract RTP from 100% to get house edge. 97% RTP means 3% house edge. Lower house edge is better for the player over long sessions.

Does volatility matter? Yes for variance shape, no for expected value. High volatility means rare big wins between many small losses. Low volatility means frequent small wins. Same RTP either way; different psychological feel.

Is bigger bet size better? No. Bigger bets just amplify variance. Pick stake size at 1-2% of session bankroll to survive realistic losing streaks. We cover this in our bankroll management guide.

Worked example to ground the theory

Take a typical session: $200 bankroll, 2x cashout target, $2 per round (1% of bankroll), 100 rounds.

Expected wins: 49 rounds at $4 each = $196 collected

Expected losses: 51 rounds at $2 each = $102 lost

Net expected: $196 - $200 staked = -$4. That is the 2% house edge over 100 rounds at this configuration.

Real session variance: most sessions finish between -$30 and +$30 around the -$4 expected. Some sessions you finish way up; some way down. The -2% only emerges as a long-run average over many sessions aggregated.

The takeaway: short-term variance is much louder than long-run expected value. Discipline lets you stay in the game long enough for the math to converge.

How this connects to broader crash strategy

This article is one piece of a larger picture. The full strategy framework involves:

1. Picking a cashout target you can defend mathematically. We cover this in our 2026 strategy guide.

2. Sizing stakes against expected streak depth. The math is in our bankroll guide.

3. Picking games with the highest RTP available to you. The ranking is in our RTP rankings.

4. Verifying provably fair on every round you care about. The process is in our verification guide.

Each piece supports the others. None of them individually beats the house edge - what they do collectively is help you survive the math long enough to enjoy playing.

Server seed plus client seed equals cryptographic key for the round. Spribe's innovation was using three client seeds from three independent players; the structural difference matters even though the underlying math primitive is the same SHA family.

Verify the seeds yourself

Open the Provably Fair Verifier (browser-only, supports all major schemes)

Recompute any Aviator (SHA-512 + 3 seeds), JetX (SHA-256 + 1 seed), Lucky Jet (SHA-256 + 4 seeds), or BGaming round in 60 seconds via Web Crypto API. Inspect the JavaScript source to confirm the math matches the documented protocol.

Open the Verifier

Frequently asked questions

What is a server seed in crash games?

A server seed is a long random hexadecimal string generated by the casino's server before each round. The length depends on the hash function: 64 hex characters (256 bits) for SHA-256 schemes, 128 hex characters (512 bits) for SHA-512 schemes (Spribe / Aviator). The seed is generated using OS-level entropy plus a cryptographic random number generator (CSPRNG), held privately on the casino's server until after the round, with only its SHA hash published pre-round. The seed is revealed in plaintext after the round ends, allowing anyone to verify the cryptographic commitment by hashing the revealed seed and confirming it matches the pre-published hash.

What is a client seed and how is it generated?

A client seed is a hex string contributed by players that combines with the server seed to determine the crash outcome. Generation depends on the provider scheme. Spribe (Aviator) pulls three client seeds from the first three players who place bets in each round; each seed is generated client-side by the player's browser via window.crypto.getRandomValues.

SmartSoft (JetX) uses one client seed contributed by the bet-placing player, typically derived from the player's account ID or a randomly-generated string. 1win Gaming (Lucky Jet) uses four client seeds for additional manipulation resistance.s four client seeds (player's own plus three from random other live participants). BGaming uses one client seed plus optional Bitcoin block hash for additional entropy on select titles.

Why does Aviator use three client seeds when other crash games use one?

Spribe's three-client-seed design is structurally stricter than single-seed schemes against manipulation. With one client seed, the seed-contributing player has theoretical (cryptographically bounded) influence on the outcome; the bound is mathematically small but the structural attack surface exists.

With three independent client seeds drawn from three random players, the attack requires compromising three independent players simultaneously, which is practically infeasible. Spribe pulls the three seeds from the first three players who place bets in each round; even the casino cannot predict which three players will contribute until the round starts. SHA-256 with one client seed is mathematically defensible in 2026 (no known practical attacks); Spribe's three-seed SHA-512 is the strictest standard tier in the regulated crash genre.

When does the casino publish the revealed server seed?

After each round ends. The reveal protocol: pre-round, the casino publishes the SHA hash of the server seed (binding the casino cryptographically); during the round, the seed remains private on the casino server; post-round, the casino publishes the seed in plaintext to the operator's UI. Anyone can hash the revealed seed via the same SHA function and confirm the digest matches the pre-published hash from before the round. Tier 1 licensed operators (UKGC, MGA, Spelinspektionen) always reveal reliably because regulators audit the protocol; offshore Curacao operators sometimes hide the reveal behind support requests or do not reveal at all (which defeats the cryptographic protection).

What if the casino does not reveal the server seed after a round?

The game is not provably fair regardless of marketing claims. The reveal is what makes the cryptographic commitment meaningful; without it, you have only the casino's word about what seed was used. Three escalating responses: first, check the operator's provably-fair settings panel for round history with revealed seeds (some operators bury it 3-4 menu clicks deep).

Second, contact operator support requesting the revealed seed for the specific round. Third, if the operator hides reveals reliably, refuse to play on that operator and switch to a Tier 1 licensed casino with audited reveal procedures. Hidden reveal is one of the strongest untrustworthy-operator signals; treat as a flag against the platform.

How do I use the seeds to verify a specific round?

Open Aviator on your operator and play a round (or open one from history). Navigate to the provably-fair panel and copy the four values: revealed server seed, client seed(s), nonce, displayed crash multiplier. Open our browser verifier. Choose the scheme matching your game (SHA-512 + 3 seeds for Aviator; SHA-256 + 1 seed for JetX; SHA-256 + 4 seeds for Lucky Jet).

Paste the values into the corresponding fields. Click Compute. The verifier hashes the inputs via the chosen SHA function, extracts the hex slice as fraction h, applies the crash multiplier formula, and displays the computed crash point. Compare with the displayed multiplier; match means the round was honest, mismatch means escalate. Total time roughly 60 seconds per round.