How to verify a provably fair crash round, step by step

What do you need before the round starts?

A provably fair check begins before you bet, not after. According to Aviator's in-game rules, each round's server seed is a string of 16 random symbols chosen by the operator, and only its SHA-256 hash is public ahead of the round. In the game menu it sits under "Provably Fair Settings", labelled "Next server seed SHA256".

Copy that hash somewhere outside the game, with the time and the game room you are in. A screenshot is enough. Without your own copy, you can only compare the game's numbers with the game's numbers.

You also need a tool that computes SHA-256 and SHA-512. Both are defined in FIPS 180-4, the Secure Hash Standard from the US National Institute of Standards and Technology (NIST), so a correct tool returns the same output for the same input. If the words seed and hash are new, read server seeds and client seeds explained first.

How does a round get its result?

The rules name four participants in every result: the operator and the first three players to bet. Each player has a client seed, made on the player's side. In settings you can leave it on "Random on every new game" or enter your own.

At take-off the three client seeds are merged with the server seed. The merged symbols are turned into a SHA-512 hash, and the round result is taken from that hash. Each game room runs its own seeds, so check rounds from the room you were in.

How do you check the round, step by step?

1. Before you bet, open the game menu, choose "Provably Fair Settings" and copy the value labelled "Next server seed SHA256". Note the time and your game room.
2. If you want your own input in the result, choose "Enter manually" and save a client seed. The rules say you cannot change it while a bet is active, and it only counts if you are among the first three players to bet.
3. Let the round run. Then open "My Bets", or the "Top" tab, and press the green fairness icon beside that round.
4. Read the window: server seed, the three player seeds, the combined SHA-512 hash, the hex and decimal values, and the result.
5. Compute SHA-256 of the server seed exactly as shown. Compare your output with the hash you copied in step 1, character by character.
6. Join the server seed and the three client seeds as the game does, compute SHA-512, and compare it with the "Combined SHA512 Hash" line.
7. Check that the result row matches the multiplier at which the round ended.

Step 5 is the core test. A match means the operator committed to that server seed before anyone bet. A mismatch means the round fails, whatever the rest of the window says.

Step 6 has a gap you should know about. The rules text says the seeds are merged, but it does not spell out the joining format. If your SHA-512 output differs, ask the operator's support for the exact format before you draw a conclusion.

How do you compute the hash yourself?

On a Mac or Linux terminal, the commands below print the SHA-256 and SHA-512 hash of a seed. Paste the seed between the quotes exactly as the window shows it.

printf '%s' 'PASTE-SEED-HERE' | shasum -a 256
printf '%s' 'PASTE-SEED-HERE' | shasum -a 512

Use printf rather than echo. By default, echo adds a line break to the end of the text, and that one hidden character changes the whole hash.

One changed symbol gives an unrelated hash. FIPS 180-4 states that any change to a message will, with a very high probability, result in a different digest, which is why a swapped seed cannot pass step 5.

What does a match prove?

A matching SHA-256 hash shows the server seed was fixed before the round and not replaced after the bets came in. The standard also calls it computationally infeasible to find a message behind a given digest, so the hash did not reveal the seed early.

A matching SHA-512 hash shows the result was produced from the four seeds in the window. Three of those seeds arrive from players after the server seed is fixed. That is why no player, and no predictor seller, can know the outcome in advance, as the guide on why Aviator predictor apps are scams explains.

What does a match not prove?

It does not prove the return to player. Spribe states a 97% RTP for Aviator, but that figure depends on the formula that turns the hash into a multiplier, and the rules text does not publish it. Long-run returns are what lab maths testing checks: BMM's mathematics page lists RTP among the figures a game submission must include, and GLI says an RNG must be fully tested for non-predictability and bias.

It does not prove the operator is allowed to offer the game in Kenya. Licensing is a separate check, set out in the guide on whether crash games are legal in Kenya.

It does not settle what happens to a bet when your connection fails, which the game rules handle separately; see what happens when your connection drops mid-round. It also cannot show who the first three bettors were, only the seeds the window lists.

Above all, it does not change your odds. The check confirms a round was not altered, and the 97% RTP explained in shillings still describes what bets return over time.

What if a round fails the check?

Keep your evidence: the screenshot of "Next server seed SHA256" with the time, the fairness window, and your bet history. Then complain to the operator in writing.

Regulation 9(2)(e) of the Gambling Control (Conduct of Gambling Operations) Regulations, 2026 requires a licensee to refer any complaint unresolved after 72 hours, or where you ask in writing, to the Gambling Regulatory Authority. The regulator's toll-free line, as shown on its website, is 0800-723-770.