Each Original commits to a server seed (SHA-256 hash shown pre-bet), accepts a settable client seed and increments a nonce per bet; results derive from HMAC-SHA256 of the triple and can be recomputed after seed rotation. Community verifiers cover Dice, Limbo and Crash; coverage for Mines/Towers is thinner because Roobet's exact message formats are not all publicly documented.
How to verify a Roobet 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
Crash
4%
4% declared edge in our catalogue; third-party estimates put it at 3.5–4%. Not published on site.
Blackjack
0.7%
Mission Uncrossable
4%
Dice
1%
Mines
4%
Keno
1%
Plinko
1%
Roulette
6.3%
6.3% declared edge in our catalogue.
Towers
4%
CoinFlip
4%
Anomalies and caveats
Roobet publishes no per-game RTP for originals on site; support quotes a ~97% average while our catalogue records a 4% declared edge on Crash, Mines, Towers, CoinFlip and Mission Uncrossable and 6.3% on Roulette.
In 2021 Roobet froze a player's $3.26M Crash win alleging cheating (publicly reported "JesseJuliano" dispute). That is a dispute-handling data point, not evidence against the PF construction — but it is the fairness-adjacent incident buyers of this report usually ask about.
Roobet is not a Crypto Gambling Foundation member; originals are self-audited rather than CGF-audited.
Anomalies describe observations from public code, documentation or reporting. They are not accusations of cheating; where something is unproven we say so.
Scoring breakdown — 6.5/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: 2/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: 1/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: 0.5/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/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.
Method and sources
Roobet fair page + community verifiers (rakestake: Dice/Limbo/Crash verified) + review dataset; incident reporting from public sources.
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.