Game Rules

Every game runs on a single configurable house-edge parameter. RTP = 1 − house edge and is identical for every strategy — no play pattern changes the expected return.

The RTP variant is fixed per deployment by the operator and never changes mid-session. Bet limits: 0.10 – 100 credits per bet.

• Place a bet during the betting phase (6 seconds). Two bet slots may be used simultaneously.
• When the round starts, the crew carries loot out of the vault and the multiplier rises from 1.00×.
• Bank any fraction (25% / 50% / 100%) of your open position at any time. Each banked amount is locked in at the current multiplier.
• The round ends at a hidden bust point. Any un-banked remainder is lost.
• The bust multiplier follows P(bust ≥ m) = (1 − e)/m, so a round can bust at 1.00× (probability e = house edge). This is where the house edge lives — every banked amount has expected value (1 − e) × stake share.
• Banking requests are executed against the server clock. Network latency may mean the multiplier at execution differs slightly from your display.

• Place a bet; the multiplier rises from 1.00× along a fixed exponential curve.
• Cash out before the hidden bust point to win stake × multiplier. Bust before cashout loses the stake.
• Optional auto-cashout executes server-side at your chosen multiplier, unaffected by connection quality.
• The bust point is drawn and cryptographically locked before the round starts. Same distribution as Banka.

• Choose a stake and 1–24 mines on a 5×5 grid. Mine positions are drawn and hash-locked before your first click.
• Each safe tile multiplies your potential payout; hit a mine and the stake is lost.
• Cash out after any number of safe tiles. Multiplier for k safe picks with m mines: (1 − e) / P(k safe picks).
• Revealing all safe tiles pays out automatically.

• Open a long or short position with leverage (1–50×). A commission of e (the house edge) is charged on open: effective position = stake × (1 − e).
• The price path is a symmetric random walk, fully drawn and hash-locked at open. Future prices are never exposed while the position is open.
• Close any fraction of the position at the current price ("take profit"). Equity multiplier: 1 + L × direction × price change.
• If equity reaches 0 the position is liquidated and the remainder is lost. With leverage L, liquidation occurs exactly at a 1/L adverse move — no gap risk.
• Positions expire after the fixed session length; any remainder settles at the final price.

AUTO-JOIN places your current stake automatically at the start of each round for a chosen number of rounds (10, 25, 50 or unlimited). Your auto-run target and banking plan, as set at the moment each round starts, apply to every automatic bet. If your previous round used both positions (A and B), auto-join repeats that setup and places both.

Settings are locked per bet. The auto-run value that applies to a bet is the one registered when that bet was placed; changing the wheel afterwards affects the next bet, never a bet already in play. The value in force is shown next to your position while the round runs.

• Autoplay stops immediately if your balance cannot cover the next stake, or if any bet is rejected.
• Exactly one automatic bet is placed per round; reconnects never place bets.
• You can stop autoplay at any time by tapping the control back to "off". Manual banking always overrides automation.
• Autoplay does not change the odds or RTP: every outcome is drawn from the same committed seed chain, and RTP is identical for automated and manual play.
• Operators may disable autoplay entirely for their market.

• All outcomes are decided server-side against the server clock. Your device only displays state.
• If you disconnect with an open position: auto-cashout (Crash) still executes; Banka/TakeProfit positions run to their natural settlement; Mines rounds remain open and can be resumed or cashed out on reconnect.
• Settlement is lazy and deterministic: the recorded outcome depends only on the locked random draw and timestamps, never on connection quality.
• Malfunction voids play: if a verifiable server error produces an outcome inconsistent with the locked seed data, affected rounds are voided and stakes returned.

Every random outcome is derived from three values: a server seed (secret), your client seed (editable in-game), and an incrementing nonce (round counter).

• Before any round, the game publishes SHA-256(serverSeed) — a binding commitment.
• Outcome derivation: HMAC-SHA256(serverSeed, clientSeed:nonce) → first 13 hex chars → uniform number → game result. The published hash proves the server seed (and thus all outcomes) was fixed before you played.
• Rotate the seed at any time to reveal the previous server seed and verify every past round yourself — each game exposes a /api/…/verify endpoint that recomputes outcomes from revealed seeds.
• Seed state is persisted server-side: the commitment chain survives server restarts.

Open the live verification terminal → (view the current commitment, rotate seeds, and recompute past rounds)

BANKA — the shared multiplayer chain

BANKA is played by everyone on the same round, so the client seed is public and shared (banker-public-v1) rather than per player. The server seed rotates automatically every 500 rounds, and the retired seed is published the moment its epoch closes — you do not have to ask anyone.

• GET /api/mp/seeds — the current commitment, plus every server seed already revealed and the exact round range it covers.
• GET /api/mp/round/{nonce} — a settled round: its outcome, the commitment it was drawn under, and the revealed server seed once the epoch has closed. A round that is still running cannot be looked up.
• GET /api/mp/verify?serverSeed=…&clientSeed=…&nonce=… — recomputes the outcome from revealed values. Or do it yourself: any HMAC-SHA256 implementation gives the same answer.
• POST /api/mp/rotate-seed — close the current epoch immediately and force the reveal. Refused while a round is running, since that would expose a live outcome.

Revealed seeds and settled rounds are stored in the server journal, so a restart or a deployment does not erase the evidence for rounds already played.

• Round IDs and timestamps (UTC) are displayed in-game and recorded in an audit ledger.
• Simulated players ("bots") may appear in multiplayer demo rounds for demonstration purposes. They are clearly a demo feature and can be disabled per deployment; they never affect your odds or payouts — each player's outcome depends only on the shared round result and their own actions.
• Max exposure per round is capped as listed in the RTP table. Bets that would exceed caps are rejected upfront.