Skip to content
Flight log / Provably fair

Lucky Jet Provably Fair: Verify a Round in 5 Steps

Yes, Lucky Jet has a working provably fair check, and it does what it says within clear limits. Before each round the client shows a hash of the result; after the round it reveals the text that was hashed, and running that text through SHA-512 reproduces the hash. A match proves that the finished round's multiplier was fixed when the round began and was not changed afterwards. It does not prove anything about how the value was generated or what the game returns over time. We traced the verification routine in the client code to confirm each step below.

In short: Lucky Jet's fairness check is real and runnable in 5 steps. It verifies one past round against a hash published at the start; it is not an audit of the random number generator or of the return figure.

How the commitment works

The commitment is a hash published before the outcome matters, and the rules describe it in four short lines. The round ends when the multiplier reaches a certain value. That value is produced on the game servers at the start of the round and is shown publicly as an encrypted Hash. At the end of the round, the same Hash is saved in history together with Salt. The Hash can then be verified in the client's Fairness Check window or with any online calculator.

In the code, the hash comes from the round state and round information the client receives at the start. The automatic check is gated: it waits until the round has both its salt and its final multiplier before running. An unfinished round shows "Round not completed" in the fields where the result will go.

What the Salt field really contains

The Salt field is not a bare salt. This is the most useful thing we found in the code, and it explains why the instruction "copy the Salt and hash it" works.

The client builds the field from three parts of the finished round: its ID, the final multiplier formatted to two decimals inside square brackets, and the server's salt, joined by plus signs. In the source the template reads:

round.id + "+[" + coefficient.toFixed(2) + "]+" + round.salt

So a copied Salt looks like ROUND_ID+[X.XX]+SALT. The multiplier is inside the hashed text. That is the whole point of the design: if anyone changed the result after the hash was shown, the hash would no longer match.

Two details from the code matter when reading a result. The recorded multiplier is the larger of 1 and the final value, so the record never shows a figure below 1.00. And the round IDs, salts and hashes shown in the client's explanation pictures are placeholders, not real rounds; they illustrate the layout only.

Verify a round in five steps

This table follows the data from the round record to the comparison, exactly as the client's own check does it.

Step Input Operation Output
1. Open the proof Shield icon in bet history or leaderboard Opens the round's record Round ID, multiplier, Salt, Hash
2. Copy the Salt The Salt field Copy as shown Composed string ID+[X.XX]+salt
3. Encode The copied string UTF-8 encoding Bytes
4. Hash The bytes SHA-512 digest Lowercase hex string
5. Compare Your hex string and the round's Hash Exact match Success or failed

Inside the client, the Fairness Check window does steps 3 to 5 for you. Its "Enter the Salt" field accepts up to 160 characters, and the code hashes whatever is typed there directly, reporting success only when the result equals the round's stored Hash. Outside the client, any SHA-512 calculator gives the same answer if it receives the exact string, with no added spaces or line breaks.

The rules screen never names the algorithm; it only says "Hash". The code does. The helper it calls uses the browser's built-in SHA-512 digest, so a calculator set to SHA-256 will fail every time, which is the most common reason a manual check "doesn't work".

What a match proves, and what it leaves open

A successful check is strong evidence about one thing and silent about several others.

Question Does the check answer it?
Was this round's multiplier fixed when its hash appeared? Yes
Was the result changed after you placed your bet? Yes, a change would break the match
Is the generator producing a fair spread of results? No
What is the long-run return to player? No
Were bets settled correctly on the server? No
Can the next round be predicted? No, its Salt stays hidden until it ends

One practical tip makes the check mean more. The commitment only binds a result if you saw the hash before the round finished, so note the Hash during the flight, or take a screenshot, and compare it with the history afterwards. A hash read only after the round can confirm the arithmetic, not the timing.

The return figure lives elsewhere. Lucky Jet's rules screen takes its RTP line from the operator's settings, describes it as a long-run average, and cautions that results over a few rounds can swing well above or below it. No hash check reaches that number.

How this compares with seed-based schemes

Some crash games mix player input into each result. Aviator, for example, blends an operator seed with seeds supplied by the first three players who bet. Lucky Jet relies on one server-generated value, which makes the check simpler, one string and one hash, but leaves the generation entirely on the server side. The trade-off is laid out row by row in Lucky Jet vs Aviator.

Verdict on fairness

Lucky Jet's provably fair feature is genuine and easy to use: five steps, one free tool, and the client even runs the comparison itself. Its scope is narrow, and that is fine as long as it is read correctly. A match tells you a finished round was not rewritten. It tells you nothing about the next round, which is why the predictor claims around this game fall apart, and nothing about the long-run return.

For the controls that come before any of this, see how to play Lucky Jet; the main guide brings the rules together. Only adults (18+) should play for money, and a fair round can still lose every stake placed on it.

FAQ

Which hash algorithm does Lucky Jet use?

SHA-512. The rules screen only says 'Hash', but the checking code in the client calls the browser's SHA-512 function, and a SHA-256 tool will never match.

Is the Salt field just the salt?

No, it holds three parts: the round ID, the final multiplier in square brackets with two decimals, then the server salt, separated by plus signs.

Does a successful check prove the RTP?

No, a match confirms only that one finished round was locked in at the start. It does not measure the generator or the long-run return.

Can I check a round that is still running?

No, the Salt appears only after the round ends. Until then the round record reads 'Round not completed' and the automatic check waits.