“Provably fair,” defined
A provably-fair crash game is one where the outcome of every round can be independently verified by the player after it happens. Instead of asking people to trust a certificate, the studio commits to the result before betting opens and reveals the proof afterwards, so anyone can recompute it. It’s the same cryptographic idea that underpins Bitcoin: trust the math, not the operator.
The commit–reveal cycle
Every round runs through four steps:
- Commit — the server generates a secret server seed and publishes its SHA-256 hash before the round starts.
- Play — players place bets and cash out. The outcome is already fixed by the seed.
- Reveal — after the round, the server publishes the seed itself.
- Verify — anyone hashes the revealed seed; it must match the hash published in step one, and the crash point must recompute exactly.
Because SHA-256 is a one-way function, the studio cannot find a different seed that produces the same hash — so it cannot change the result after bets are placed. The outcome is mathematically locked the moment the hash is public.
The crash-point formula and house edge
A good provably-fair game also publishes the exact function that turns the seed hash into a multiplier. A widely-used formula carries a transparent ~1% house edge (i.e. ~99% RTP), where roughly 1% of rounds resolve at 1.00×. The key word is transparent: the edge is a visible property of the published formula, not a hidden “instant-bust” layered on top.
How a player verifies a round
In practice the player copies the revealed server seed into a verifier, which re-hashes it and recomputes the crash point. If both match the values shown before and during the round, the round was fair. You can try our live verifier right now — paste any seed and watch the hash and crash point compute in your browser.
Why it matters for operators
Players increasingly expect verifiable fairness, and regulators reward transparency. Offering provably-fair crash games reduces disputes, builds trust faster with crypto-native audiences, and differentiates you from operators still running black-box titles. For a studio, refusing to publish the method is a red flag — fairness you can’t check is just marketing.