Crash at Tonza: one shared round and why your exit point doesn't change the return

Crash at Tonza: one shared round and why your exit point doesn't change the return

Crash differs from every other Tonza Originals game in one way: the round is shared. In coinflip, dice or mines each player has a private conversation with the server — you press, you get an outcome. Here the round runs on its own, everyone sits in the same one, and the crash point is identical for all of them. Everything else follows from that, including the answer to the question every player asks: is there a winning exit strategy?

How a round works

A round has three phases. First seven seconds of betting — enough time to get in. Then the flight: the multiplier climbs from 1.00× along an exponential curve. At any moment you can cash out and receive your stake times the current multiplier. At some point the round breaks — that is the crash, and everyone still in it loses their stake. Four seconds later the next round begins.

The pace is fixed: reaching 1.50× takes about 3 seconds, 2× takes 5.3, 5× takes 12.4, 10× takes 17.7. Fast enough to stay tense, slow enough to change your mind.

Where the probability actually lives

The crash point is not "roughly random" — it comes from a strict distribution. The chance of surviving to multiplier x is:

P(x) = (1 − house edge) / x

At our current 2% edge that gives:

MultiplierChance to reachPayout on a $10 stake
1.50×65.33%$15.00
49.00%$20.00
32.67%$30.00
19.60%$50.00
10×9.80%$100.00
100×0.98%$1,000.00

Why no exit point beats another

Multiply any row: chance to reach, times the multiplier. Every row gives the same number — 0.98, or 98% of the stake. That is not a coincidence but a direct consequence of the formula: if the chance is (1 − edge) / x and the win is x, the average product is always (1 − edge), whatever x you pick.

The practical conclusion is worth understanding before your first bet: your exit point changes variance, not return. Cashing out at 1.20× wins often and small. Waiting for 20× wins rarely and large. Over a long run both hand the house the same share. What differs is the shape of the path: a flat line with occasional dips, versus long droughts with rare spikes.

No system gets around this. Doubling after a loss, waiting out a run of low rounds, following someone else's auto cash out — all of it moves risk around in time without changing a single number in the table above. Rounds have no memory: the crash point is derived from this round's seed and its number, and ten 1.00× in a row tells you nothing about the eleventh.

Why more than 2% of rounds end at 1.00×

Watch the history long enough and you will notice roughly 3% of rounds ending at exactly 1.00×, while the house edge is 2%. The gap is rounding, not rigging.

The multiplier is shown to two decimals and rounded down. A round whose true crash point landed at 1.004 displays as 1.00 — and from the player's side that is indistinguishable from an instant crash, because cashing out below 1.01 is impossible either manually or automatically. That effect contributes about 0.95 percentage points, which together with the 2% edge produces the observed 2.97%.

It does not affect payouts. The chance of reaching any multiplier from 1.01 upward stays exactly (1 − edge) / x, and the return stays exactly 98%. We deliberately did not tune the share of 1.00× rounds down to match the edge: any such tuning would break the main formula, and with it your ability to verify a round.

Auto cash out, and why the server owns the multiplier

Auto cash out is the multiplier at which your bet is taken without you. It helps twice over: it removes the need to hit a specific tenth of a second, and it removes your connection from the equation — a manual tap can arrive late on a poor line, while auto cash out is settled on the server.

The same point answers a common question: the multiplier your payout is calculated at is decided by the server on its own clock, not by your browser on yours. The figure on screen is drawn from a formula against the round's start time, and it deliberately lags the server's slightly. That way you never receive less than you read. The opposite order would mean "cashed at 2.10, paid at 2.08", and there would be no honest way to explain it.

How to verify a round

Crash is verified differently from our other games — again because the round is shared. There is no client seed: one crash point for everyone cannot depend on any single player's seed. Instead of the usual trio of server seed, client seed and nonce, you need three other values: the round seed, the round number and that round's house edge.

The seed hash is published before betting opens — it sits right under the game field. The seed itself is revealed immediately after the crash rather than at rotation: it belongs to the round, not to a player, so there is nobody left to hide it from. The rest is computed in your browser on the fairness page: HMAC-SHA256 over the seed and the round number, 52 bits taken as a number between zero and one, and the formula returns exactly the crash point you watched.

You can verify any round, including ones you did not play — it is shared. The procedure itself is covered in how to verify your round.

Worth remembering

  • Return is identical at any exit point — only variance changes.
  • Rounds are independent: a run of low multipliers says nothing about the next one.
  • Auto cash out does not improve the math, but it removes reaction time and connection from it.
  • The maximum possible crash point is 1,000,000×, at odds of roughly one in a million.
  • Stake size matters more than multiplier choice — see bankroll management.

Worth reading