GAME GUIDE · LIMBO

How Limbo Works: Target Multiplier, Hit Chance and 99% RTP

Threshold Limbo now uses the production server runtime. Choose a target multiplier and Transaction Core completes RNG and settlement before the frontend presents the result. The round wins only when result is at least the target.

RTP
99.00%
Target
1.01×–1,000,000×
P(win)
0.99 ÷ Target
Runtime
Server-authoritative

How to play

  1. Enter a wager of at least 0.1 COIN in 0.1 COIN increments and choose a Target multiplier, or derive the target from win chance.
  2. The frontend submits wager, target, client seed and idempotency key. Transaction Core creates and settles the round.
  3. If result ≥ target, payout = bet × target; otherwise payout is zero. Wallet, ledger, round and balance values come from the server response.
  4. The central counter animates from 1× to the already-settled result and does not alter the outcome.

Limbo math

The model uses P(win)=0.99/Target. Since a win pays the Target multiplier, ideal expected payout is Target×0.99/Target=0.99, corresponding to 99% RTP and about a 1% house edge. Production uses fixed-point arithmetic and a 52-bit discrete RNG implementation whose quantization does not increase RTP above 99%.

Target 2×49.50%Expected wait ≈ 2.02 rounds
Target 10×9.90%Expected wait ≈ 10.10 rounds
Target 100×0.99%Expected wait ≈ 101.01 rounds

Fairness and settlement

Transaction Core creates and settles Limbo rounds using server crypto / HMAC RNG, commitment / reveal, immutable casino rounds, GAME_BET / GAME_PAYOUT ledger mutations and serializable transactions. The frontend does not decide result, payout, net or balance.

Frequently asked questions

Is a higher target better value?

No. Hit probability falls as 0.99/Target, so a larger multiplier does not increase expected value.

After many low results, is a high result due?

No. Independent random outcomes do not become due because of history.

Is the result still being drawn while the counter animates?

No. Server settlement is already complete; animation only reveals the settled result.

Can a retry charge twice after a network failure?

An uncertain wager reuses its original idempotency key so the server resolves the original round instead of intentionally creating a second wager.