GALABET FAIR / ONE SHARED FLIGHT
Crash.
The flight ends at a recorded multiplier. Follow a completed example, then check the hash link and calculation that describe its last moment.
Public hash-chain replay · no live round or cash-out
COMPLETED PUBLIC EXAMPLE
5.95×Final multiplier recorded.
THE FLIGHT LOG
Two checks.
One recorded ending.
A matching link connects the revealed hash to the previous one. A second calculation uses the hash, salt and declared edge to reproduce the multiplier.
- Previous published hash
- 9883ff7c598d3c0ebfabf0b1965074955d8874806ff39443ff55536f81212af1
- Revealed game hash
- 85a96b33e69fe1bdfd99d97e021112182907781e4b501bd208e27a47a85a3739
- Public example salt
- galabet-design-review-public-salt
- Declared edge
- 1%
FOLLOW THE CHAIN BACKWARDS
The flight can end.
The record stays.
- 01
Check the link.
Hash the revealed game hash with SHA-256. Compare it with the previous published hash. A match connects this entry to its neighbour in the chain.
SHA-256(gameHash) = previousHash - 02
Reproduce the multiplier.
Use the game hash, salt and declared edge to calculate the same endpoint. Crash uses the first 52 bits of its HMAC digest, rather than the four-byte fraction used by Dice.
crashResult(gameHash, salt, houseEdge) - 03
Keep timing separate.
A matching calculation does not prove that a cash-out request arrived in time. A live service also needs authoritative round phases and a confirmed action log. This page replays an already public example.
THE SERVER'S ROUND CLOCK
A flight has phases.
An action has a receipt.
The multiplier animation is a view of the round. The server decides whether an action arrived during an allowed phase. That distinction matters when a request is delayed or a player reconnects.
- 01 / WAITING
Accept the stake.
Associate it with one chain and round index. Once the phase changes, a late bet cannot join that flight.
phase: "waiting" - 02 / RUNNING
Record the accepted action.
A manual cash-out needs a server response identifying the round and accepted multiplier. A button press alone is not that response.
phase: "running" - 03 / CRASHED
Finish and disclose.
Publish the endpoint and game hash. Keep the completed result available when a socket reconnects.
phase: "crashed"
ILLUSTRATIVE REQUEST LOG
Two requests can leave the same screen and reach different phases.
These entries explain the distinction; they are not events from the public 5.95× replay above.
round 184 · action received
accepted multiplier 2.14×The server receipt records the accepted action.
round 184 · action received
phase crashed · rejectedA stale on-screen multiplier cannot reopen the round.
For a reconnect, restore the current phase and the player's acknowledged action before resuming animation. Hash verification checks the endpoint; an action log addresses timing. Live service integration remains separate from this explanatory replay.
REFERENCE EXAMPLE / PUBLIC HASH CHAIN
Check the link and the finished multiplier
import { verifyCrashLink, crashResult } from '@galabet/fair';
const gameHash = '85a96b33e69fe1bdfd99d97e021112182907781e4b501bd208e27a47a85a3739';
const previousHash = '9883ff7c598d3c0ebfabf0b1965074955d8874806ff39443ff55536f81212af1';
const salt = 'galabet-design-review-public-salt';
console.log('link', await verifyCrashLink(gameHash, previousHash));
console.log('result', await crashResult(gameHash, salt, 0.01));link true result 5.95×
The example salt and hash are public fixtures. They demonstrate the calculation and make no claim about external randomness or a running production chain.
CRASH & AVIATOR-STYLE FLIGHT GAMES
Build the flight
on Galabet Crash.
Choose your stake and start a flight.
Automatic cash-out stays active if you disconnect. Manual cash-out uses the multiplier accepted by the server.
Free practice only. Credits have no monetary value. This session lasts up to 24 hours and resets if the practice server restarts.
Building your own Aviator-style flight game? Galabet’s Crash calculation gives you the endpoint behind the rising multiplier. Connect it to an aircraft, a rocket or your own flight scene, and keep the hash-chain record available for every completed round.
Connect your scene to the round.
Use the waiting, running and crashed phases to coordinate take-off, the multiplier display and the end of the flight. Galabet’s backend includes Crash chain management and stored round history. Connecting your interface and cash-out flow to those services is part of your game integration.
Give the result a second look.
After the flight, the revealed game hash, salt and declared edge let you reproduce the endpoint with Galabet. A player can check the calculation; a developer can investigate a mismatch using the same inputs. Keep accepted cash-out actions alongside that record to explain the player’s outcome.
Follow the Crash calculation ↗