NEXTGROUND · provably fair
Committed before.Revealed after.
A crash game hashes a seed into one multiplier. Ours draws every tick of the path from it, so what you check is the whole round and the collapse it ends on. Put two seeds in the panel below and it runs, in this tab.
18+ · Simulation · Play money · No real wagering
Two seeds in. The round they make, out.
How a round is sealed.
Before the round
The server commits
SHA-256(server seed)
A seed is drawn and hashed, and the hash is published while betting is still closed. Nothing about the round can change after that line is printed.
Before the round
The player contributes
client seed
It enters the keystream next to the server seed, so neither side alone decides the path.
During the round
The keystream draws every tick
HMAC-SHA-256(seed, client | market | round | tick)
Eight 32-bit words per tick, divided by 2^32, twenty times a second.
After settlement
The seed is revealed
server seed
Hash it: you get the commitment printed before the round. Feed it back: you get the same path, tick for tick.
Any time after
Anyone replays it
the whole path, not one number
The panel above does it, and so can anything that speaks HMAC-SHA-256.
What this rules out.
Ruled out
The operator picked the outcome after seeing the bets
A different path means a different seed, and a different seed means a different hash, published before betting opened.
Ruled out
The path was nudged mid-round against a large position
Replay the round and any nudge shows up as a divergence at a named tick.
Ruled out
The house replays the same rounds for everyone
Two players on the same market and round number get different paths, because the client seed is in the keystream.
Ruled out
The published round is not the round that was played
The collapse tick and the mark it ends on are part of what gets checked, not just the seed.
Not applicable
The game is free of a house edge
It is not, and no fairness scheme makes it so. The edge is the spread, 3.00% on the round trip, plus a 2.00% retention on drift while a position is open. Both are visible on screen while you hold.
There is no system.
Close at 1.50
96.43%
0.73
Close at 2.00
96.15%
1.01
Close at 3.00
95.32%
1.41
Timed exit at 5 s
96.80%
0.41
Timed exit at 30 s
94.75%
1.64
Trailing stop −15%
95.42%
1.54
Dip-buy cycle (+25% / −7%)
95.11%
0.69
Hold to collapse
0.00%
0.00
The line is the published return, 97.04%
Eight strategies replayed on the same 120,000 simulated CORE rounds, stake 1.00, entered at listing at the ask. Return is the bid received over the ask paid; a round-trip that never closes returns zero.
What the player sees.
- Before each round
- The commitment, in full, while betting is still open. HMAC-SHA-256 keystream, server seed committed before each round.
- After each round
- The server seed, next to the commitment it hashes to. Copy either one out.
- While a position is open
- Bid and ask drawn around the price, so the 3.00% spread is a distance on screen, not a line in a paytable.
- Whenever you ask
- Realized return to player, live, as returned over turnover. It converges on the published figure as rounds accumulate.
Replayed it? The integration is five calls.