What integration involves
- Load the bridge script and take the seed and session from it; the game never calls Math.random.
- Run a fixed-timestep simulation so the same seed reproduces the same run for every player.
- Respect the hard score bound and the canonical scoring specification written for the title.
- Post throttled live telemetry, which is never authoritative, and submit the terminal result once.
- Go through bot-driven calibration, which derives the title's difficulty bands and certified ceilings before it reaches players.
How the platform protects your title
Signed and settled once
HMAC-signed sessions; wager and currency read from the database; duplicate submissions return the prior result.
Score rules
Server-side rules, duration and rate checks, calibrated ceilings and a live-telemetry cross-check can reject implausible scores before a reward is paid. Rejections are logged.
Modes you do not build
Solo, Arena head-to-head with escrow and rematch, missions and tournaments are platform functions with backend-authoritative rules; the game reports a result and the platform does the rest.
Where your games run
On every brand that switches them on: skill titles pay into the brand's Gold Coin and Sweeps Coin wallet and appear in its library, tournaments and Arena. Operators choose games per brand with feature toggles, so a title can be live on several brands from one integration.
The integration guide, the bridge script and the scoring specifications are shared under NDA once a demo has established fit. Commercial terms for studio content are discussed on the demo.