How Crash games work: the math behind the curve
Crash is the purest casino game — bet, watch a multiplier rise, cash out before it breaks. The interesting part is that the 'random' crash point is fully public math.
If you have ever played on Stake, BC.Game, Roobet, or X24, you have seen Crash. A green curve rises exponentially; players cash out in real time; eventually the curve breaks and everyone still in the round loses their bet. The mechanic is trivial. The math — and why it is fair — is the part worth understanding.
The crash point is decided before the round starts
A common misconception is that Crash is “random as it goes.” It is not. The moment the round starts, the final crash multiplier is already fixed. The curve you see is just a cosmetic animation rising towards a predetermined target. When the clock hits that target, it breaks. Period.
The crash point comes from the provably-fair hash:
- Take the first 8 hex chars of
HMAC_SHA256(serverSeed, clientSeed:nonce). - Cast to a uniform float
rin[0, 1). - If
r < houseEdge(typically 1%), crashPoint = 1.00 — an insta-crash. - Otherwise,
crashPoint = floor(100 · (1 - houseEdge) / (1 - r)) / 100. This produces the log-distributed crash curve you see in the history chart.
Why the exponential curve feels fair
The log-distribution has a magical property: the probability you survive to a multiplier m is (1 - houseEdge) / m. Cash out at 2x? Roughly 49.5% chance. Cash out at 10x? 9.9%. Cash out at 100x? 0.99%. The multiplier and survival odds are perfectly reciprocal, which is why the EV is flat.
That is also why aggressive strategies do not beat Crash long-term. A “always cash out at 1.1x” strategy wins often but grinds down slowly; a “always target 100x” strategy loses 99% of rounds but pays when it hits. Both lose 1% of their stake on average. The only real choice is variance.
Auto-cashout vs. manual
Most Crash clients let you set an auto-cashout multiplier before the round. Use it. A manual cashout that should have fired at 1.50x but fired at 1.48x because of a 30ms network blip is an unforced error. Auto-cashout is executed server-side: your target is stored with your bet, and the server fires the cashout the moment the curve reaches it — no network in the path.
Shared multiplayer vs. solo rounds
There are two flavours:
- Shared lobby (the Stake/Roobet model). One round at a time, runs globally. A 7-second intermission lets everyone bet before the curve starts. You see other players cash out live on the feed — social, laggy, slightly addictive.
- Solo round. Your bet, your curve, your nonce. Faster pace — you can queue the next round while the previous one finishes. Less social but better for bankroll grinding.
X24 ships both. The lobby is at /play/originals/crash.html, alongside the 6 other X24 Originals — Mines, Dice, Plinko, Wheel, HiLo, and Limbo (instant-target Crash).
Is there a 'pattern' to Crash?▾
No. Each round is independent and derived from a fresh nonce. Gambler's fallacy does not apply — a string of low crashes does not make the next one more likely to be high.
What happens on network disconnect mid-round?▾
Auto-cashout runs server-side, so it fires regardless of your connection. Manual cashouts depend on the packet reaching the server before the curve crashes — exactly what auto-cashout eliminates.
Why do some Crash games feel 'luckier' than others?▾
Usually that is just variance. If the house edge and RTP are identical (both 99%), the long-term EV is identical. Short-term streaks can look dramatic but do not indicate a rigged system.