Recompute the Limbo crash multiplier from your revealed seeds — with the formula checked bit-for-bit against Stake's own calculator.
Computed locally via the Web Crypto API (HMAC-SHA256) — no server call. Your seeds and nonce never leave your device. It's the same code we test against Stake's own calculator.
In Limbo you pick a target multiplier and win if the round's multiplier lands at or above it. A single float becomes that multiplier. Sounds simple — but it's the game where verifiers most often go wrong.
The result comes from the standard Stake-style byte stream:
HMAC-SHA256( key = server_seed , message = "client_seed:nonce:round" )
One float f maps to the multiplier:
crash = 16777216 / ( floor( f × 16777216 ) + 1 ) × 0.99The key is 16777216 = 2²⁴. Many popular open-source Limbo verifiers use 1e8 instead and produce a wrong multiplier at the extremes — e.g. 3,807,692× where Stake's own calculator returns 3,321,888×. Ours matches Stake's reference exactly. The +1 also prevents a divide-by-zero when f = 0.
One float f is turned into 16777216 / (floor(f × 16777216) + 1) × 0.99. That 0.99 is the 1% house-edge factor applied to the raw multiplier.
Because many use 1e8 instead of 2²⁴ (16777216). At high multipliers the two diverge — the 1e8 version is wrong. We verified ours against Stake's own /provably-fair/calculation page.
No. With the server seed still hashed, the multiplier is unknowable. This tool only checks a round after the seed is revealed.
Yes — Stake, Stake.us, Rainbet, Roobet, BC.Game, Shuffle and clones share the same Limbo math.
Formula verified bit-for-bit against Stake's reference calculator (Aug 2026). Other games: Dice · Limbo · Plinko · Mines · Keno · all verifiers. Open methodology: /methodology/. © FairPlay Audit — independent, free, open-source.