How to Verify a Crash Round Yourself, and What It Does Not Prove

Both of those are worth understanding before the procedure is worth running.

The procedure

1. Before the round. The server generates a secret seed and publishes its SHA-256 hash. The hash is a commitment: it is computed from the seed, but the seed cannot be recovered from it.
2. During the round. Client seeds are contributed by players. The operator cannot know them in advance, so it cannot pick a server seed that produces a chosen outcome.
3. After the round. The server reveals the secret seed.
4. Check one. Compute SHA-256 of the revealed seed. It must equal the hash published in step 1. If it does, the seed was fixed before you bet.
5. Check two. Combine the server seed with the client seeds exactly as the operator documents, and recompute the round result. It must equal what the game showed.

If both checks pass, the outcome was determined before any money was on the table. That is the whole guarantee, and it is a real one.

What it proves

• The result existed before your bet and could not respond to it.
• The operator could not see the bet total and then choose an outcome.
• Nothing was altered between the round ending and the payout.

What it does not prove

• That the house edge is what is advertised. Commit and reveal proves the result was not tampered with, not that the underlying distribution is the published one. A build that produced crash points from a 90% curve would still verify perfectly on every round. The distribution is what certification labs test, and it is a different question from fairness of a single round.
• That the game is beatable. Verification is backwards-looking. It confirms a finished round. It gives you nothing at all about the next one, because the next seed is not yet revealed and the rounds are independent.
• That the site is the genuine build. A clone can publish hashes that verify against its own seeds while running entirely different maths underneath.

The check that actually matters day to day

Verify one round when you start on a site, to confirm the mechanism exists and works. After that, the useful audit is the distribution one: for a crash game, the chance of reaching multiplier m should be about RTP divided by m, and you can sample the round history to see whether it looks like that. For Dice or Limbo, multiply the shown win chance by the target and see what return figure comes back. Those tests examine the thing provably fair leaves untouched.

Quick answers

Does provably fair mean the game is fair? It means the round was not manipulated after bets were placed. It says nothing about whether the payout distribution matches the advertised RTP.

Can verifying rounds help me predict the next one? No. Verification only works on finished rounds, and each round is independent of the last.

What if the hash does not match? That is the one genuine red flag, and it means the seed was changed after the commitment. Stop playing there.

Reviewed by the PlayStories editorial team. Last updated July 26, 2026. Numbers verified per our methodology. Informational only, not betting advice. 18+. Play responsibly.

Related

• What provably fair means
• Is Aviator rigged?
• Is Mines rigged?
• How an RNG actually works