Casino integration, built on evidence.
A transparent engineering handoff for casino operators, platform teams and independent test laboratories.
No games are currently independently certified or approved for real-money distribution.
Static Riot does not claim certification, regulator approval, a certified RNG, or a certified RTP. Current profiles and reports are in-house development evidence. A qualified independent test laboratory and the relevant regulator must assess and approve each game and deployment for the intended market.
Development evidence
- Versioned server-side game and math profiles, with pinned profile hashes on rounds.
- Server-generated outcomes, immutable round history and signed wallet transaction receipts.
- Integer minor-unit wager validation, idempotent requests, recovery and bounded reconciliation.
- In-house simulations, deterministic fixtures, cap checks and wallet failure/replay coverage.
- Original art, audio and game design provenance records are maintained as review material.
These records help a lab begin its review. They are not a lab report, RNG certificate, source-code audit, IP clearance or jurisdictional approval.
Controlled profiles; no invented RTP claim
- Dead Voltage math profiles are marked as candidate/development profiles; reported RTP values are not independently established theoretical RTP.
- Outlaw’s Go Wild and Dracula’s Lair complete-round maximum award is capped at 10,000× base bet.
- Dracula’s 2,000,000-round exploratory run did not observe a cap outcome; this does not establish cap probability or RTP.
- Bonus costs, stake ladders and awards are server-validated. Client animation does not determine outcomes.
Before lab submission, freeze one profile per game and market, publish the complete math specification, calculate theoretical return and feature contribution independently, characterize hit frequency/volatility/tails, document RNG seeding and state handling, then reproduce the approved hash from the exact submitted build.
Integration contract and deployment handoff
The current signed RGS is a development-only HMAC integration. It pins the operator, player, currency, game, stake ladder and math profile at launch. Wallet debit/credit/rollback operations use stable transaction IDs and receipt validation; unresolved rounds can be recovered and reconciled.
Operator responsibilities
- Provide a fixed HTTPS wallet adapter with atomic idempotency and permanent transaction lookup.
- Keep operator credentials server-side; sign requests with timestamp, single-use nonce and HMAC-SHA256.
- Configure a market-approved currency and server-owned stake schedule; never accept a client-provided ladder.
- Complete parallel, timeout, duplicate, insufficient-funds, interrupted-settlement and ledger reconciliation tests.
Current limits
- Development mode only; no real-money launch path.
- External signed launch supports Dead Voltage, Outlaw’s Go Wild and Dracula’s Lair in development mode. Market configuration, partner acceptance and production controls remain open.
- HMAC v1 does not include response HMAC or mutual TLS. Production key management, allowlists, monitoring, incident response, SLOs and a security review remain open.
- Game build, wallet, currency, jurisdiction and stake configurations require partner acceptance before any production plan.
Independent certification pathway
- Agree target countries and distribution model with the licensed operator; confirm regulator, testing standards, submission format and approval route.
- Freeze each game’s source, build, configuration, math profile, RTP target, stake schedule, paytable, bonus rules, cap and RNG implementation.
- Prepare controlled lab package: source and reproducible binaries, architecture, RNG design, mathematical model, simulation tools/results, test vectors, security controls, version hashes and change history.
- Submit to a laboratory accepted by the target regulator for independent RNG, game math, game implementation and security testing; remediate findings under change control.
- Complete the relevant regulator’s game approval/type approval and operator-specific certification or notification steps.
- Run operator integration/UAT, independent wallet ledger reconciliation, load/security/monitoring checks, responsible-gambling and player-information review, then sign a market-specific distribution agreement.
- Release only the approved artifact and profile. Monitor integrity and incidents; route every material math, RNG, game or platform change through impact assessment and any required retest/reapproval.
Which laboratory, technical standard and regulator apply depends on the operator and target jurisdiction. The operator and specialist counsel should confirm the route before a formal submission.
DISCUSS AN OPERATOR PROJECT ↗