Crash point maths: from a hash to the multiplier a round ends on

From seeds to a hash

Spribe prints a small illustration of its own. The page joins «AB», standing in for the server seed, with «CD», standing in for a player seed, and shows «ABCD»; beneath it sits the SHA512 hash, a 128-character value opening with 49EC55BD83FC, and a round result of 25.00. The first half of the illustration can be repeated by anyone: hashing the four characters ABCD with a standard SHA512 tool returns exactly the string on the page, character for character.

Three properties of a hash function make it useful here. The same input always gives the same output. A change of one character in the input produces an output that looks entirely unrelated. And there is no practical way to run the function backwards from output to input. The first property makes a round reproducible; the second and third turn a published hash into a binding commitment.

Wolfbet prints a complete mapping for one of its own games, dice, and it shows the shape such mappings share. The server seed, together with a message made of the client seed, an underscore and the nonce, goes through HMAC-SHA256. The first five hexadecimal characters of the output are read as a number between 0 and 1,048,575; if it is 1,000,000 or more, the next five characters are used instead; the accepted number is reduced modulo 10,000 and divided by 100 to give a roll between 0 and 99.99. That is a dice procedure, not a crash one, but the pattern is general: a slice of the hash is read as a number and scaled to the game's range.

From a hash to a crash point

For a crash title the last step has to turn the hash into a multiplier somewhere between 1.00x and the title's ceiling. SmartSoft's page confirms the floor for JetX, which can end as early as 1.00x, and Turbo Games gives the top for Crash X and Aero as ×999,999. Spribe says that round results are generated from the SHA512 hash and that each game uses slightly different mathematics to suit its requirements; the function for any single title is kept inside the game.

So the useful question for a player is not what the exact function is, but whether the number shown in the round history came from the hash the game committed to. That is a matter of checking, and the procedure is laid out in a four-value walk-through. Where this step sits among the stages of play, from the commitment to the stop, is shown on the round anatomy page.

Floors, ceilings and the spread between them

Two numbers frame every value a title can end on. The floor is where the climb starts and the lowest stop there is: 1.00x on JetX, and x1.00 as the starting value on Aero. The ceiling is the most the design allows: ×999,999 for both Turbo Games titles, while Spribe and SmartSoft print no top value for Aviator and JetX.

Between the two lies the spread of stopping values, and that is where each title's character lives: how often rounds end almost at once and how often they run long. No studio page opened for this guide publishes that spread. A figure invented to fill the gap would be worse than none, so this page gives no odds of reaching any particular multiplier.

Where the house edge sits

A return figure below 100% has to come from somewhere, and in a crash title it lives inside the mapping. The conversion from hash to multiplier is built so that, averaged over a very large number of rounds, the amount paid back falls short of the amount staked. Spribe puts Aviator's return at 97%, so the edge on that title is 3%. Turbo Games prints 96% for Crash X and Aero, an edge of 4%. JetX's published range, 96.2%–98.9%, means an edge anywhere from 1.1% to 3.8%, and the casino's configuration decides where in that band a given lobby sits.

The edge never appears inside a single round. A round that stops at 40x shows no visible deduction; the edge is a property of the whole spread of stopping values, not a fee taken from one of them. As an illustration of what the figure describes, not a forecast: 1,000 rounds at 1 unit each put 1,000 units at risk, and at a 97% return the long-run expectation of the design is about 970 units back. A real run of 1,000 rounds can land well above or well below that. More on reading these percentages is in studio return figures.

Why past crash points are no guide

Every round's number comes from its own inputs: a new server seed in Spribe's per-round design, a new nonce in the seed-and-nonce design Wolfbet describes. Hash outputs for different inputs bear no usable relation to one another, which is the second property above at work. A string of stops under 2x does not make a high one more likely next, and a very high stop does not use anything up.

The round history and statistics that game screens show, such as the ones JetX's page lists, are records of the past. Nothing in a list of earlier stops can predict the next one, because the next value depends on a seed still hidden behind its hash. Any app or channel claiming otherwise is selling something the mathematics does not contain. What a player can usefully set is the exit, and presets and their arithmetic show what that choice does and does not change.

What a published hash proves about the number

A matching hash shows that the seed behind a round is the one committed before the stakes arrived, so the crash point was not swapped once the bets were known. It shows nothing about how generous the mapping is, and it does not touch a casino's own terms on identity checks or withdrawals. The full list of what the check does and does not cover sits on the fairness explainer.

RNG titles

Not every crash game ties its crash point to a published hash. On its JetX page SmartSoft attributes the height of the multiplier to random generation and sets out no seed verification, so a JetX round cannot be recomputed from values a player holds. For such titles the stated return range and the studio's own description are what a player has to go on. The terms used across these pages are defined in the crash glossary.

Frequently asked questions