Server seed rotation: what retiring a seed reveals and what it closes

What server seed rotation reveals

Wolfbet tells players that, to check earlier bets, they must reveal the server seed by generating a new one in the «Session» menu. The act does two things at once. The old seed appears in full, so it can be hashed and compared with the hash issued earlier. And every bet placed under it becomes recomputable, one nonce at a time.

This is the payoff: a whole run of bets can be checked against a single commitment. The procedure for doing so, with a worked example based on Wolfbet's printed dice procedure, is on the round-check page.

What rotation commits

The new server seed is hidden again behind a fresh hash, and the cycle starts over. Wolfbet's page adds that the nonce is reset when the server seed changes, so the first bet under the new seed begins the count afresh. Bets under the old seed and bets under the new one therefore form two separate chains, each tied to its own commitment.

What rotation closes off

Rotation reveals a seed; it does not recreate anything you failed to keep. If the hash issued before the old seed's first bet was never saved, the revealed seed can be hashed, but there is nothing independent to set it against. If you changed the client seed partway through, the bets before and after the change used different inputs, and each part needs its own client seed. And because the nonce restarts, the numbering of the old chain is only as good as your notes.

Put simply, rotation opens the past to checking only as far as your records reach. Save the hash, the client seed and the nonces before you retire a seed, not after.

A worked sequence

Here is how the pieces fit, as an example with invented numbers rather than a real account. You open a session and copy the hash of the server seed the casino has issued. You place 40 bets, and after the 25th you replace your client seed, so bets 1 to 25 use the first client seed and bets 26 to 40 the second. Then you generate a new server seed in the «Session» menu.

The old seed now appears. You hash it and compare the output with the hash you copied at the start; if they match, all 40 bets came from the promised seed. Each of them can then be recomputed from that seed, the client seed active at the time and its own nonce. Meanwhile the replacement seed sits behind a new hash, which you copy before the next bet, and a new count begins with it.

Changing the client seed

The client seed is the player's own input. Wolfbet says the client seed is the player's to change whenever they choose, and that each change begins a new chain of results. Its FAQ (2 September 2026) describes the server seed as replaceable either per session or per bet ID. Spribe offers the client-seed change in its «Provably Fair Settings» window, next to the hash of the next server seed.

Changing the client seed is not the same as rotating the server seed. On Wolfbet's description, only generating a new server seed reveals the old one, so a new client seed alone opens nothing to checking. What it does do is make sure that part of every future input comes from you.

Rotation in a per-round design

Spribe's scheme asks for no server seed rotation from the player. The settings window lists the upcoming seed's SHA256 value, and once the round ends the history window displays that seed alongside the players' seeds, the joint SHA512 value and the outcome. Each round, in effect, retires its own seed. Turbo Games' Aero page follows the same per-round pattern: the hashed seed is shown ahead of the betting phase and the seed itself is disclosed at the end.

The practical difference is timing. In a per-round design every round becomes checkable as soon as it ends, and the only value you must capture in advance is the hash. In a seed-and-nonce design nothing is checkable until you rotate, and you need the nonces as well. The wider scheme, and what it does not prove, is on the fairness explainer.

Before you rotate: a short list

1. Copy the hash of the current server seed, if you have not already.
2. Write down the client seed, and every earlier client seed used under the same server seed.
3. Note the nonces of the bets you want to check, or the range they fall in.
4. Rotate, then copy the revealed seed at once, together with the hash of its replacement.

When a result looks wrong

If a bet ever looks odd, rotation is what turns a suspicion into something you can test. Before it, the only evidence is a hash. After it, the seed, the client seed and the nonce allow the bet to be worked out again and set against the result you saw. Rotate, run the check, and only then decide whether there is anything to raise with the casino's support, taking the saved values with you. Each operator's terms and clauses are collected in the casino fact boxes.

What rotation does not change

A new seed is as indifferent to your results as the old one. Rotating after a run of losses leaves the return of every game where it was, and the house edge stays where the studio put it: 3% for Aviator at its 97% return, 4% for Crash X and Aero at 96%. Those figures are unpacked on the RTP and edge page. Rotation never predicts anything either; it only makes a finished chain checkable. Terms such as nonce, hash and client seed are defined in the crash glossary.

Frequently asked questions