Seed Rotation
Seed rotation is the process by which a crash game replaces one or both cryptographic seeds used to generate round outcomes, ensuring that no single seed pair is used indefinitely and that the game’s provably fair system remains trustworthy over time.
In provably fair crash games, each round result is produced by combining a server seed (held by the casino) and a client seed (contributed by the player or browser). Together they determine the multiplier at which a round crashes. Seed rotation is the scheduled or on-demand replacement of these seeds. When a rotation occurs, the old server seed is revealed in hashed or plain form so players can verify every round that was played under it — then a fresh seed pair takes over for future rounds.
Rotation matters for fairness because a seed that never changes would give a dishonest operator the theoretical ability to predict and manipulate future outcomes while keeping the same hash commitment. By rotating seeds regularly — after a set number of rounds, at a player’s request, or on a fixed schedule — the casino limits the window in which any single seed pair is active. Provably fair platforms like Pigaboom implement transparent seed rotation so players can audit the full history of any completed seed cycle at any time.
In practice, seed rotation works like this: before a new server seed goes live, the casino publishes its SHA-256 hash. You record that hash. After the seed is retired through rotation, the casino reveals the original seed value. You can then hash it yourself and confirm it matches what was committed — and use it alongside the client seed to recalculate every multiplier from that cycle. If any result doesn’t match, the game’s fairness is compromised.
Players can usually trigger a manual seed rotation from their account settings between rounds. Doing so ends the current seed cycle immediately, unlocks the previous server seed for verification, and starts a new committed cycle. Rotating your client seed periodically is considered good practice if you want independent checkpoints in your verification history.
See also: how to verify a crash game result