B2B crash game platform · seamless wallet

The curve climbs. The books balance. Every single round.

Your games, our engine, your wallet. Players' money never leaves your systems — games embed in an iframe, every bet settles over an HMAC-signed server-to-server API, and every crash point is committed to before the round starts.

// server-authoritative · integer minor units · no floats in money

betting ×1.00
busted
commitsha256 …

Not a video. Real math, live in your browser — the production curve m = ek·t with a real sha256 commit–reveal on every round.

97–99%
RTP, configurable per game
100 ms
authoritative multiplier tick
0
floats in any money path
1 tx
database transaction per round settlement

Integration

Three moving parts. Two of them are ours.

You keep the wallet and the player. We run the game, the math and the ledger. A typical integration is measured in days, not months.

STEP 1

Launch in an iframe

Your backend issues a one-time token and opens /play/game/{id}/play.html?token=…&operator=you. No SDK on the page, nothing to bundle — the game client ships from our origin (or your CDN).

STEP 2

Expose your wallet

Six HTTPS endpoints on your side — login, balance, bet, win, refund, logout — HMAC-SHA256 signed, idempotent by transactionId, retried from a durable outbox until acknowledged.

STEP 3

Settle and verify

Each round settles in one database transaction on our side and reconciles against your wallet to the cent. Crash points are provable by anyone through the public fairness verifier.

Games

One engine. Every skin plays for real.

A game is a folder: manifest, theme, scene. The math, wallet, fairness and protocol underneath are identical — certify the engine once, launch skins forever. Try each one on fun money, no signup.

Flagship

Sky Ace

The aviation classic, tuned hot: two bet slots, auto-bet, live chat and freebets riding a 99% RTP curve.

RTP 99.0%max ×5002 slotschat
Turbo

Crash Drift

Blink and it's boarding again: a 4-second betting window and a queue that never lets a round leave without you.

RTP 97.0%max ×1004s bettingbet queue
Mechanics

Gold Rush

For prospectors with nerve: bank half mid-climb and let the rest ride — or insure the whole dig before takeoff.

RTP 98.0%max ×300partial cashoutinsurance

Adding a skin touches zero engine code — it is a folder with a manifest, not a fork.

Feature catalog

Flags in a manifest, not forks in a codebase.

Every feature below is a per-game flag. Turn it on for one brand, off for another — the money core never changes, and features that change the math ship only after the simulator has replayed them across millions of rounds.

Bet mechanics

  • Multi-slot — two independent bets per round
  • Auto cashout with one-tap presets (×1.5 / ×2 / ×5 / ×10)
  • Auto-bet with stop conditions
  • Bet next round — queue a bet mid-flight
  • Turbo rooms — shortened phase timings per room

Cashout mechanics

  • Partial cashout — bank half, let the rest ride
  • Bet insurance — refund if the round busts early
  • Side bets — over/under on the crash point
  • All math-changing features are simulator-gated before rollout

Trust

  • Provably fair — sha256 commit–reveal hash chain
  • Public verifier — anyone can recompute any round
  • Client seeds (optional, Aviator-style)
  • RTP certificate generated by the same code that runs live

Promo

  • Free bets — issued over signed S2S or from the admin panel
  • Rain — split a drop across live players in a room
  • Tournaments and missions on settled rounds
  • Per-merchant promo limits enforced before issuance

Social layer

  • Chat + reactions with rate limits and mutes
  • Leaderboards — daily / weekly / all-time
  • Big-win ticker across the room
  • Strictly best-effort: can never touch the money path

Operations

  • Multi-currency — one room per currency, per-currency limits
  • Private tables per brand, shared or isolated
  • Admin panel — RBAC, TOTP, append-only audit log
  • Observability — Prometheus metrics, alerts, runbooks
  • Responsible gaming — reality checks, limits, self-exclusion

A feature that is absent from a game manifest simply does not exist for that game — clients hide it, servers reject it. One flag: features.partialCashout: true.

Provably fair

We couldn't rig a round if we tried. Here's the proof.

Every room consumes a precomputed sha256 hash chain. The hash is committed before betting opens and revealed after the bust — so neither we nor the merchant can steer a round, and any player can check any round after the fact.

C

Commit

Before betting opens the client receives prevHash — the sha256 of the hash that will decide this round. The chain's terminal hash is published when the chain is provisioned.

R

Reveal

When the round busts, the round hash is revealed. Anyone can check sha256(hash) == prevHash — the commitment made before any bet was placed.

=

Recompute

The crash point is a pure function of the revealed hash: recompute it in the public verifier, or in your own code from the formula on the right.

crash point — bustabit v2games-math
// r = RTP (e.g. 0.99), hmac = HMAC-SHA256(salt, roundHash)
X     = uint52(hmac) / 252            // uniform [0,1)
crash = max( 1.00, floor( 100·r / (1−X) ) / 100 )

// properties, for r = 0.99:
P(crash ≥ m)     = r / m
P(instant bust)  ≈ 1.98%
median crash     ≈ ×1.98

Get started

Ship a crash game this quarter. Not next year.

Feel the engine on fun money first — the demos run against a live platform environment. Then read the wire format: launch, wallet API, protocol, math, mechanics. Six endpoints stand between you and a certified crash title.