Check the commitment, random draws and outcome of a completed game.
How case results are generated
Before play, the server seed hash, client seed and next nonce are available in your seed settings. The opening freezes its case version, quantity and borrowing percentage.
The draw process
HMAC-SHA256 uses the server seed bytes as its key. Its ordered message contains the protocol, draw domain, client seed, nonce, case draw index, ticket range and rejection attempt.
Each opening uses one nonce; a multi-case opening uses a different zero-based draw index for every case. Starting a battle you created also uses your next nonce, so your case and Deal games can skip a number.
Rejection sampling maps the 256-bit digest to an integer ticket without modulo bias. Frozen cumulative item weights select the item.
Borrowed openings keep the unborrowed percentage of each item value, rounded to the nearest cent, as credit.
Verify your opening
Rotate your seed pair in Settings after completing the opening. This reveals the old seed and creates a new commitment for future play.
Enter the game ID. The verifier checks every ticket and item against the original case version, including borrowed payouts.
A game whose owner has a private profile is visible only to that owner.
Cases settle instantly. Their server seed is revealed when the pair is rotated, not after each opening.
