Server Seed

Server seed is a secret string of data generated by the casino’s server that, combined with a client seed, produces the provably fair outcome of each crash game round.

In provably fair crash games, the result of every round is not decided in the moment — it is pre-determined by cryptographic inputs before the round begins. The server seed is the casino’s contribution to that process. Before a round starts, the casino publishes a hashed version of the server seed (a scrambled fingerprint). This means the casino commits to a fixed value without revealing it, so neither the player nor the house can manipulate the outcome after the fact.

Once a round ends, the casino reveals the original server seed. You can then combine it with the client seed and a nonce (round counter) and run the same hashing algorithm yourself to reproduce the crash multiplier independently. If the result matches what the game showed, the round was fair. This is the core of provably fair verification. Games like Pigaboom implement this system so players can audit every result without relying solely on the casino’s word.

A practical example: suppose the casino hashes its server seed and shows you a3f9…c12b before the round. After the round, it reveals the full seed. You feed that seed, your client seed, and the round number into the published algorithm. If you get a 3.41× multiplier and the game recorded 3.41×, the proof holds. If the numbers differ, something was tampered with.

One important caveat: the verification only works if you record or note the hashed server seed before the round plays out. Checking it afterward without that pre-round hash gives you no tamper-proof guarantee, since a dishonest operator could swap seeds retroactively.

Understanding the server seed is the first step to independently auditing any crash game result and holding platforms accountable for fair play.

See also: how to verify a crash game result