How do I verify an Aviator round is provably fair?

Take the SHA-256 of the revealed server seed and compare it to the server seed hash shown before the round. Then take the SHA-512 of the server seed combined with the three client seeds and compare it to the round hash in the fairness panel. If both match, the round's inputs were committed in advance and not altered.

Can this tool calculate the exact Aviator multiplier?

No. Spribe does not publish its exact hash-to-multiplier formula and provides no official test vectors. This verifier shows an illustrative multiplier from the common public crash model and clearly labels it as non-official. For the exact multiplier, compare against your operator's fairness panel.

Does provably fair mean Aviator is not rigged?

Provably fair only proves the casino committed to a result in advance and did not change it. It does not prove the operator runs the genuine Spribe engine, nor that the game is generous. Independent statistical audits are still needed to assess overall fairness.

Aviator Verifier — Check if Your Provably Fair Round Was Fair (Free)

Step 1 · Server-Seed Commitment (SHA-256)

Before each round, Aviator shows a hashed server seed. After the round the plain server seed is revealed. Paste both — if the SHA-256 of the revealed seed matches the hash shown earlier, the casino could not have changed the seed after seeing the bets.

Revealed Server Seed (shown after the round)

Server Seed Hash (shown before the round, SHA-256)

Step 2 · Combined Round Hash (SHA-512)

Aviator builds each round's hash from the server seed plus the client seeds of the first three bettors. Paste all four seeds and the round hash from the fairness panel. Because operators format the combined string differently, pick the separator/order that matches your panel (or paste the exact combined string).

Server Seed

Client Seed 1

Client Seed 2

Client Seed 3

Separator (between seeds)

Order

Expected Round Hash (from fairness panel — optional)

OR — exact combined string (overrides the fields above)

Step 3 · Multiplier — Illustrative Model Only

This turns the SHA-512 hash into a crash multiplier using the common public crash-game formula. Run Step 2 first.

⚠️ Honest disclaimer: Spribe does not publish its exact multiplier formula, and there are no official test vectors. The number below uses a widely-cited generic crash model (h = first 13 hex of the hash; multiplier = floor((100·2⁵² − h) / (2⁵² − h)) / 100). Treat it as illustrative. The real integrity proof is Step 1 + Step 2 — for the exact multiplier, compare against the value in your operator's fairness panel.

Apply 1-in-33 instant-crash rule (≈3% house edge)

Step 4 · Help the Independent Audit (optional)

FairPlay runs large-scale statistical audits of crash games. You can anonymously contribute this round to our public audit database. We store only the seeds, hashes and multiplier — never anything that identifies you — and re-verify every submission server-side. The more rounds people contribute, the stronger and more independent the analysis becomes.

Reported multiplier (optional — the result Aviator showed, e.g. 2.47)

Yes — contribute this round anonymously to the FairPlay audit database.

Private by default: nothing is sent unless you tick the box and click. Uses the seeds you entered in Steps 1–2.

What this tool proves — and what it can't

"Provably fair" does not mean "you will win". It means the casino committed to a result before you bet and can't change it afterwards. This verifier checks exactly that commitment:

Step 1 (SHA-256) proves the server seed existed and was locked in before the round — the casino couldn't swap it once bets were placed.
Step 2 (SHA-512) proves the revealed seeds genuinely produce the round hash the casino published — no silent substitution.
Step 3 is illustrative only, because Spribe keeps its exact hash-to-multiplier conversion proprietary. We show the common model transparently rather than pretend we have Spribe's secret formula.

What it still can't rule out

Even a perfect hash match can't prove the operator ran the genuine Spribe engine, that the client seeds came from real independent players, or that the game is generous. Spribe's engine is deployed across thousands of casinos and nobody independently checks each deployment. That gap is exactly why we run large-scale statistical audits — see our "provably fair ≠ fair" breakdown and the Aviator predictor scam analysis.

Step-by-step: where to find the seeds in Aviator

The exact wording differs slightly between casinos, but the flow is the same everywhere Aviator (Spribe) runs:

Open the round history. In the Aviator window, find the list of past multipliers (usually a bar of green/blue numbers along the top). Tap it to expand "My bets" / "All bets" / "Previous hands".
Pick the round you want to check and tap it. Next to the result you'll see a small 🛈 / fairness / "Provably Fair" icon — tap that.
The fairness panel opens. It shows: the Server Seed (revealed after the round), the Server Seed hash (shown before the round), three Client Seeds (from the first three players), and a combined / round hash.
Copy them into this tool:
- Server Seed hash → Step 1, field "Server Seed Hash". Revealed Server Seed → Step 1, "Revealed Server Seed". Tap Verify Commitment.
- Server Seed + the three Client Seeds → Step 2. Paste the round hash into "Expected Round Hash". Tap Compute SHA-512.
- If it says "mismatch", switch the separator or order in Step 2 until it matches your casino's panel — that combination is how your operator builds the string.
Can't find the panel? Some operators only reveal the server seed after you rotate/change your client seed in settings, or hide fairness behind the round's "…" menu. If it's missing entirely, that itself is a red flag worth noting.

Play other games? Use our all-games provably fair verifier for Stake, BC.Game, Roobet, Blaze, Rollbit, Shuffle and more.

Aviator Provably Fair Verifier

What this tool proves — and what it can't

What it still can't rule out

Step-by-step: where to find the seeds in Aviator