Don't trust us. Verify.
Every bet stores its server seed hash, server seed, your client seed and the nonce. Once a bet settles the seed is revealed, so anyone can recompute the outcome and confirm the result was fixed before the wager.
Server seed
A 32-byte secret is generated server-side. Its SHA-256 hash is shown to you before you bet, so the seed is locked in advance.
Client seed
Your own seed, editable from any game panel. We cannot change it, and it goes into every calculation.
Nonce
A counter that increases by one for each bet you place, so two identical seeds still produce different results.
Result
HMAC-SHA256(server seed, `${client seed}:${nonce}`) is read as a number between 0 and 1 — that number is the roll.
Per game
Dice & Plinko
A single float from the HMAC output drives the outcome. Dice wins when the roll is below your win chance; Plinko turns the same float into twelve left/right pegs.
Mines
Mine positions are shuffled from the same HMAC stream, so the layout is sealed before your first reveal and never changes mid-round.
Crash
Rounds run on a shared clock. Each round's seed is derived from its index and hashed in advance; the crash point comes from that seed, revealed once the round ends.
Plinko paytable
12 rows, 13 buckets. High risk pays 170× at the edge and 0.2× in the centre.
Checking a bet
Open your history, pick a settled bet and copy the seeds. Recompute the HMAC with any library and compare it against the recorded roll. If the hash of the revealed server seed doesn't match the hash published with the bet, the bet is void.
