Loading...
Every game outcome on RustRush is generated from cryptographic inputs using HMAC-SHA256. The server commits to randomness before gameplay by publishing a hash. After you rotate your seed, the raw server seed is revealed so you can independently verify that each result was derived from the committed inputs. Multiplayer games use precommitted public blockchain entropy for additional transparency.
HMAC-SHA256(serverSeed, clientSeed:nonce:gameType:roundId[:externalSeed])Look up any game by type and ID to verify its outcome.
Enter a game type and round ID to verify. The server will look up the revealed seed and recompute the outcome.
Game Type: case_open
Round ID: The unique case open ID (each open in a multi-open is separate).
Result: The roll [0, 1) is mapped to a ticket number from 1 to 10,000. Each item is assigned a contiguous range of tickets proportional to its drop chance. The item whose ticket range contains the drawn ticket is selected.
A secret 32-byte random value generated by our server. It is one of the inputs to the HMAC that determines your game outcome. The raw seed is never shown until you rotate it.
The SHA-256 hash is a one-way commitment. It proves the server seed was determined before you played, without revealing the actual seed. This prevents the server from changing the outcome after seeing your bet.
A value you control. You can change it to any string you want. It is included in the HMAC computation, giving you direct influence over the randomness generation.
A counter that increments by 1 with each game you play under your current seed pair. It ensures every game produces a unique result even with the same server seed and client seed.
An optional EOS blockchain block hash included in the HMAC for additional external entropy. When available, it makes the randomness dependent on a public, immutable third-party source.
When you click 'Rotate & Reveal'. This deactivates the current seed pair and generates a new one. All games played under the old seed become verifiable — the server uses the revealed seed internally to recompute and confirm the outcome.
A mismatch between the computed hash and the stored hash would indicate tampering. This should never happen. If you encounter a mismatch, please contact support immediately.