Stake Client Seed Explained: What It Does (and What It Doesn't)

Published 2026-04-04 · Tags: guides, verifier, fundamentals

The client seed is your part of the provably-fair math. Full explanation of what changing it actually does, plus the superstitions about it that don't hold up.

The client seed is the one piece of Stake's provably fair system you fully control. Change it whenever you want, pick anything you want, it's yours. This post explains exactly what it does, what it doesn't do, and the superstitions about client seed that don't actually affect outcomes.

What a client seed is

In Stake's provably fair system, each bet's outcome is computed as:

HMAC-SHA256(server_seed, client_seed + ":" + nonce)

The three inputs:

Server seed: secret, generated by Stake, committed via hash before you bet (see our server seed post)
Client seed: a string you provide and can change at any time
Nonce: a counter that increments per bet (0, 1, 2,...)

The client seed is typically a random 10–20 character string. By default Stake generates one for you; you can replace it with any text you want.

What the client seed does

It's a salt. Its job is to ensure that two users with the same server seed from Stake don't get the same bet outcomes. Without it, every user would share identical streams of random numbers, which would be a problem if, e.g., Stake accidentally reused a server seed.

By adding a per-user value to the HMAC input, each user's bet stream is unique even if somehow they share server seeds.

Practically: the client seed is mathematical noise. It randomizes the output, but once chosen, it's as random as any other value.

What the client seed does NOT do

This is where superstitions come in:

It doesn't "predict" outcomes

Your client seed is an input to HMAC-SHA256. HMAC is cryptographically secure, there's no relationship between the choice of client seed and the shape of outcomes. Changing from "abc123" to "xyz789" gives you a completely different, but equally random, stream of outcomes. Neither is "luckier."

It doesn't "unlock" hidden patterns

Some players try specific client seeds (famous quotes, birthdays, etc.) believing certain seeds produce better outcomes. They don't. The output of HMAC-SHA256 is indistinguishable from random for any input; no seed is luckier than another.

It doesn't expire

Client seeds stay active until you change them. There's no "seed degradation." The only thing that changes session-by-session is the nonce (increments) and, after rotation, the server seed.

What changing it DOES do

It resets your nonce to 0. Every time you change the client seed, the counter restarts.
It produces a new stream of outcomes. Same server seed + new client seed = totally different bet outcomes than before.
It gives you a fresh start feeling. Purely psychological, but real for many players.

Use cases:

You had a terrible streak and want to feel like the session is "new", change client seed
You're rotating servers + starting fresh
You want a specific seed for record-keeping ("I'll use session-04-23 as my seed so I can find it later")

Can someone else see your client seed?

Your client seed is public — it's displayed in the seed info panel alongside the server seed hash. Anyone who has your server seed AND your client seed AND your nonce range can compute your exact bet outcomes.

Usually no one has all three. But:

Our Verifier asks you for all three so it can audit bets, you paste them
If someone screenshots your seed panel, they have two of three (they'd also need to know your nonce range)
Stake's backend has all three (that's how they run the math)

The client seed being public is fine because you can't cheat with it. Even knowing all three values, you can't change the outcome, you can only verify it.

Should you pick your own client seed?

Preference, not math. Stake's default random seed is just as random as any you'd pick. Choose your own if you want to be able to recognize it later (e.g. for record-keeping on what session was which).

Some players use their wallet address or a favorite number. Doesn't matter. The HMAC-SHA256 produces the same distribution of outcomes regardless.

The "I got unlucky after changing my client seed" superstition

Players notice: they change client seed, then lose the next few bets, and conclude "I should change back."

The math: you had a 99% RTP session. You changed seed. The next bets are a fresh sample from a 99% RTP distribution — independent of what came before. If you lose 5 in a row, it's exactly the same probability (about 3%) as losing 5 in a row right before the seed change. Your brain is noticing the sequence because you did something between them, but correlation isn't causation.

Our Bet Analyzer shows your realized RTP across all your bets. If you separate your history by pre- and post-seed-change, you'll see approximately the same RTP in both halves (within variance). The seed change is mathematically invisible to outcomes.

How to change your client seed

Open any Originals game
Click the seed icon (usually a cog or "Provably Fair")
Find the Client Seed field
Type a new string (any text, usually 10–20 chars recommended)
Save / confirm

Your nonce resets to 0. From this point forward, all bets use the new client seed.

Does Stake see my new client seed?

Yes, Stake's server receives your client seed and uses it as an HMAC input. They need it to compute outcomes.

They can't do anything with it that disadvantages you, though, the server seed is the cryptographically meaningful input. Your client seed is just a public salt.

The one scenario where client seed matters

Verifying old bets after rotating servers.

To verify a bet, you need the server seed + client seed + nonce. If you change client seed mid-session, you've created a "before change" subset and an "after change" subset — each with its own client seed.

If you later want to audit old bets from the before-change subset, you need the specific client seed that was active for those bets. Stake's bet history should include the client seed that was active per bet, but if you don't save it explicitly, you might have trouble later.

Best practice: when you change client seed mid-session, screenshot both the old and new seed. Our Bet Archive export includes the client seed per bet (it's in the JSON), so even if you forget, the export has it.

Using a specific seed for superstition

If you have a personal favorite:

Use it. It doesn't hurt anything.
Don't expect it to give you luck, it won't.
Record it for your own archival purposes if the session goes memorable.

If you don't have a favorite:

Let Stake's default random seed do its thing. It's as valid as any other.

Our observation on client seed and player psychology

Players who change client seeds mid-session are often in the middle of a downswing. The act of changing feels like taking action. Mathematically it changes nothing about expected outcomes; psychologically it might help some players reset their mindset.

A better signal: if you find yourself changing client seed during a session, consider ending the session instead. The urge to change seed usually reflects tilt or frustration. Seed changes don't fix that; walking away does.

Big picture

The client seed is the part of provably fair that you own. It's public, changeable at will, cryptographically a simple salt, and mathematically neutral with respect to outcomes. Pick whatever you want, change it when you want, don't assign it powers it doesn't have.

Verify any bet using server seed + client seed + nonce. Open the Stake Verifier →