1. Server seed
Before a result is created, LuckBattle generates a secret server seed and publishes its SHA-256 hash. That hash commits us to the seed before it is revealed.
Fairness
Provably Fair
Every supported game result is generated from a server seed, your client seed, and a nonce. You can inspect your seed pair, rotate it whenever you want, and independently verify completed rounds.
2. Client seed + nonce
Your client seed is combined with the server seed and a nonce. The nonce increases with each round, so every result is generated from a unique set of inputs.
3. Verify the result
When you rotate your seed pair, the previous server seed is revealed. Hash it to confirm the original commitment, then replay the same inputs to confirm the result.
What can I verify?
- The revealed server seed matches the hash shown before your round.
- Your client seed and nonce were used in the result calculation.
- The same inputs always produce the same deterministic output.
- No one can change a committed server seed after you play.
Verify a completed round
Choose one of your historical bets. Once its seed pair has been rotated, LuckBattle will load the proof and reproduce the recorded game outcome automatically.
Manual verifier
You can also paste proof inputs manually. Add the original server-seed hash to verify the pre-bet commitment.
Change your client seed
Your client seed is combined with LuckBattle's committed server seed and a unique nonce to generate each round.
Sign in to view your active seed pair.
Saving rotates the entire seed pair. Your previous server seed is revealed, a new server seed hash is committed, and the next nonce resets to 0.
Revealed seed-pair history
Every retired pair is listed here with its original commitment and revealed server seed. Active server seeds are never exposed.
Verify randomness
After rotating, compare the revealed seed with its committed hash, then reproduce a round from the same inputs.
SHA-256(serverSeed) = serverSeedHash
HMAC-SHA256(serverSeed, clientSeed:nonce:round)