Provably Fair
Every outcome is generated with cryptographic randomness you can verify yourself.
Last updated: July 17, 2026
How it works
- Server seed: a secret random value we generate. You see its SHA-256 hash before you bet, which locks it in — we can't change it later without breaking the hash.
- Client seed: a value tied to your session that mixes into the result.
- Nonce: a counter that increases with every bet, so each result is unique.
Each outcome is derived from HMAC-SHA256(server seed, client seed:nonce). Because the server seed was committed as a hash up front, and the client seed and nonce are known, anyone can reproduce and confirm the result.
Verifying a result
After a game, you can reveal the server seed and confirm that its hash matches the one shown before the bet, then recompute the outcome yourself using the seed, client seed, and nonce. Use the verifier at /verify.
Crash works differently — and here's why
Every other game here gives you your own outcome, from your own seed. Crash can't: everyone in a round watches the same curve, so the round needs one outcome that belongs to all of you rather than one per player.
- Round seed: generated when betting opens, and its SHA-256 hash — the commit — is published immediately, before a single bet is taken.
- The commit is stored on your bet. It's written into your bet record at the moment you join, so it can't be restated afterwards.
- The seed is revealed when the round busts, and the crash point is HMAC-SHA256(round seed, round number).
To check a round: confirm that SHA-256 of the revealed seed equals the commit you were shown, then recompute the crash point from the seed and the round number. /verify covers the per-bet games; for a crash round use /api/games/crash/verify?roundId=, which returns the commit, the revealed seed and the crash point together.
House edge
Provably fair means the outcome is honest, not that you'll win. Every game carries a mathematical house edge, so results are random and fair but favor the house over time — just like any casino. See Responsible Play.
Server-side integrity
Outcomes are computed on the server with cryptographically secure randomness. Bets are authenticated, rate-limited, and protected against replay and duplication, so results can't be tampered with from the browser.