Rainbet Originals are served from dedicated subdomains (originals/crash/roulette/case-battles.rainbet.com) and present the standard commit-reveal seed-pair UI. Community verifiers treat Rainbet as Stake-engine compatible. From the shipped bundles: no payout table and no house-edge figure reaches the browser, so edge numbers live server-side and cannot be audited from the client alone.
How to verify a Rainbet 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
Dice
1%
Plinko
1%
Mines
3.5%
3.5% declared edge — unusually high for mines.
Keno
1%
Blackjack
0.4%
0.4% declared edge, the cheapest blackjack in this set.
Limbo
1%
Wheel
4%
Rock Paper Scissors
2%
Tower
4%
Chicken Cross
4%
HiLo
4%
Anomalies and caveats
No payout table ships in the browser bundle; edge figures are server-side and changeable without a front-end deploy (WagerDB bundle audit, 2026-08-16).
The geo-blocking screen is drawn in the browser and skipped for bot user agents (same audit) — a content-integrity observation, not a game-fairness one.
Our catalogue records 3.5–4% declared edges on Mines, Wheel, Tower, Chicken Cross and HiLo while Dice/Plinko/Keno/Limbo sit at 1%.
Anomalies describe observations from public code, documentation or reporting. They are not accusations of cheating; where something is unproven we say so.
Scoring breakdown — 7.5/10
Verifiability: 1.5/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: 1.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.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.
Method and sources
WagerDB static analysis of Rainbet production bundles (2026-08-16, see /research/house-edge) + community verifier compatibility + review dataset.
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.