Two fairness generations run in parallel. Legacy games use a bustabit-style chain: millions of SHA-256 hashes generated in advance, terminal hash published, played in reverse, first round mixed with a future Bitcoin block hash. Since April 2024 the newer games use a verifiable random function (RFC 9381, SECP256K1_SHA256_TAI): each round publishes a proof anyone can check against Rollbit's public key, with user id, game name, nonce and an optional user seed as input — no seed reveal needed at all.
How to verify a Rollbit round
Save the committed server-seed hash (or the published chain/proof values on chain- and VRF-based games) before playing.
Set your own client seed where the scheme supports one.
After the session, rotate the seed pair or open the revealed values; confirm the revealed seed hashes to the commitment.
Recompute the round from the revealed values with the operator’s published per-game formula or our seed verifier.
A mismatch on any single round — after checking encoding and nonce indexing — is the only evidence of tampering that actually means something.
Originals and declared house edge
Verification proves a round was not altered after the bet; the declared edge is applied openly in the payout table and is unaffected by any of this.
Game
Declared edge
Notes
Mines
2%
ECVRF-verified since 2024 (proof checked against Rollbit's public key).
Plinko
1%
Crash
5%
5% declared edge.
Flip
2%
Roulette
5%
Rollercoaster
not declared
Rollbit Bonanza
4.1%
Jackpot
not declared
Anomalies and caveats
Two coexisting fairness models with different verification steps per game; the legacy chain games give the player no per-round input.
No declared RTP for Rollercoaster and Jackpot in our catalogue; Crash and Slide (roulette) carry a 5% declared edge — five times the category norm.
Anomalies describe observations from public code, documentation or reporting. They are not accusations of cheating; where something is unproven we say so.
Scoring breakdown — 8/10
Verifiability: 2/2 — Can a player independently recompute a round end-to-end? 2 = full commit-reveal with a public algorithm; 1.5 = verifiable with caveats (mixed or partially undocumented constructions); 1 = commitment check only; 0 = nothing to check.
Player control: 1.5/2 — Does the player influence the draw? 2 = settable client seed, rotation reveals the server seed, per-bet nonce; 1 = player input absent on some games (e.g. hash-chain titles); 0 = no player input at all.
Documentation: 2/2 — Public documentation quality. 2 = per-game algorithm detail and/or sample code or a working verification sandbox; 1 = generic commit-reveal description; 0 = none found.
Edge transparency: 1/2 — Is the price of each game stated and stable? 2 = per-game RTP/house edge published and consistent with our catalogue; 1 = published but with gaps, wide spreads or marketing mismatches; 0.5 = dynamic/undisclosed edge behaviour; 0 = nothing published.
Track record: 1.5/2 — Known fairness-relevant incidents. 2 = none found; 1.5 = minor or contested; 1 = material public disputes relevant to trust in the fairness claim.
The score grades the fairness system and its transparency, not the casino overall. It says nothing about licensing, solvency or withdrawal reliability.
Analysis based on public documentation, community verifiers and — where noted — the operator's public client-side JavaScript, snapshot 2026-08-18. Constructions can change; the date matters.