Every game outcome on CaseRush is generated from cryptographic inputs using HMAC-SHA256. The server commits to its randomness before play by publishing a hash. After you rotate your seed, the raw server seed is revealed so you can independently verify that each result came from the committed inputs. Multiplayer games also use precommitted public blockchain entropy.
HMAC-SHA256(serverSeed, clientSeed:nonce:gameType:roundId[:externalSeed])The first 8 hexadecimal characters of the HMAC are converted to a number in [0, 1) by dividing by 2^32 (0x100000000).
The roll is mapped to the rules of the selected game: item selection, winner determination, crash multiplier, roulette color, or another documented outcome.
Loading your seeds…
Look up a game by type and ID to inspect its fairness record and verify its outcome when the seed is available.
Game Type: case_open
Round ID: The unique case-opening ID. Each opening in a multi-open has its own ID.
Result: The roll in [0, 1) maps to a ticket from 1 to 10,000. Each item owns a continuous ticket range proportional to its drop chance. The item whose range contains the drawn ticket is selected.
A secret random 32-byte value generated by the server. It is one input to the HMAC that determines the game outcome. The raw seed is hidden until you rotate it.
The SHA-256 hash is a one-way commitment. It proves that the server seed was fixed before you played without revealing the seed itself. This prevents the server from changing the outcome after seeing your play.
A value you control and can change to any string. It is included in the HMAC calculation, giving you direct influence over the randomness inputs.
A counter that increases by one with every game under the current seed pair. It makes every result unique even when the server seed and client seed stay the same.
An optional EOS blockchain block hash included in the HMAC as additional external entropy. When present, the randomness also depends on a public, immutable third-party source.
When you choose “Rotate & Reveal.” The current seed pair is deactivated and a new one is generated. Games played with the old pair can then be recomputed and verified with the revealed server seed.
A mismatch between the computed hash and the recorded hash can indicate tampering. If you find a mismatch, save the game or round ID and contact support immediately.