Provably FairEvery result on DLBattle can be checked by you — no trust required.
1We commit
Before you play, we create a secret server seed and show you its SHA-256 hash. The hash locks the seed in — we can’t change it later without the hash changing.
2You add your seed
Your client seed is mixed in, so we can’t predict results either. Change it any time. A nonce counts up by one every bet.
3You verify
Rotate your seed to reveal the old server seed. Enter it below: we hash it to check it matches, then recompute every result from SHA-256(server:client:nonce:i).
Verify a result
Your seeds
Rotate a seed in any game’s Provably fair panel to reveal it here, then press Verify.
| Game | Bets | Revealed seed |
|---|
How each game uses the floats
- Float: first 13 hex characters of
SHA-256(server:client:nonce:i)÷ 252 — a number from 0 to 1. - Dice: roll = ⌊float₀ × 10001⌋ ÷ 100 (0.00 – 100.00).
- Keno: Fisher–Yates shuffle of 1–40 with floats 0–38; the first 10 numbers are drawn.
- Mines: Fisher–Yates shuffle of tiles 0–24 with floats 0–23; the first m tiles are bombs.
- Plinko: one float per row — below 0.5 bounces left, otherwise right. Bin = number of right bounces.
- Upgrader: roll = float₀. Roll under wins when roll < chance; roll over wins when roll ≥ 1 − chance.
- Cases: float i opens case i, walking the item list (in “What’s inside” order) weighted by drop chance.
- Case Battles: each spin uses
SHA-256(server:client:nonce:round:seat:k), first 8 hex ÷ 232. k = 0 decides an ult spin, k = 1 picks the item, k = 3 the hero, k = 4 the item on an ult spin.