An Aviator round is decided by a hash computed before the betting window opens

The cycle runs about 20 seconds. The server generates a seed, combines it with seeds from the first 3 players, hashes the result with SHA-256 and publishes that hash. Only then does betting open. The multiplier you watch is a rendering of a number that already exists.

Verified 2026-08-30

The round, step by step

• The server generates its seed and collects client seeds from the first players entering the round.
• It hashes them together and publishes the hash. The outcome is now fixed and public in sealed form.
• The betting window opens for a few seconds. Nothing you do here changes the sealed number.
• The plane takes off and the multiplier climbs from 1.00x on a fixed curve.
• At the predetermined point it stops. Anyone who cashed out before keeps stake times multiplier.
• The seeds are revealed so the round can be verified against the hash published at step two.

Where each piece lives

Round outcome

operator server, before the round

Verification hash

published, before betting

The multiplier curve

rendered on your device from the server result

Your cash out

sent to the server, timestamped there

Stake limits

set by the operator

The 97% return

set by Spribe, identical everywhere

That table is the answer to most predictor questions. Nothing that decides the outcome runs on your phone, so nothing installed on your phone can change it.

Why the curve looks accelerating

The multiplier rises faster as it climbs, which makes high multipliers feel closer than they are and compresses the decision window. That is a design choice about how the number is displayed, not about probability. The chance of reaching x remains about 0.97 divided by x throughout.

What auto cash out changes about the cycle

Your exit is registered server-side at the multiplier you set, rather than depending on a tap arriving in time. Same expected return, one fewer way to lose a round you meant to exit.