Provably Fair
Check any result yourself. The check runs in your browser, and the same steps open on CodePen.
Every coinflip, jackpot, case opening, and case battle on RBX Grim is decided by a value that exists before you bet and can be recomputed by anyone afterwards. You do not have to trust us. You can check it yourself.
How a result is made
We commit first
Before a coinflip, jackpot round, or case battle takes a single item, we generate a 32 byte server seed and publish its SHA-256 hash. Case openings run on a personal seed pair committed the same way. The hash is visible from the moment the game exists and it cannot be changed later.
You supply the other half
The result also depends on a client seed we do not control. On coinflips, jackpot, and case battles it comes from every player in the game, mixed with an EOS block that had not been mined when the game locked. On case openings you can set the client seed yourself.
The result is derived
Both inputs go through HMAC-SHA256. The first 8 characters of the digest become a number between 0 and 1. There is no step anywhere where a result gets picked.
We reveal and you check
Once the game settles we publish the server seed itself. Hash it and you get the commitment from the start of the game. Run the HMAC and you get the same roll we used. Both checks run in your browser, and again on CodePen if you want a page we do not host.
Coinflip
The client seed is the SHA-256 of both player ids by seat. When the game fills we lock in a future EOS block number and later mix that block's id into the seed. Each side's chance to win is its share of the pot, so a bigger wager wins more often.
clientSeed = SHA-256( creatorId:0 | opponentId:1 ) roll = HMAC_SHA256(serverSeed, clientSeed + ":" + eosBlockId + ":0") roll = first 8 hex digits / 4294967296 creator wins when roll < creatorValue / (creatorValue + opponentValue)
Jackpot
The client seed is the SHA-256 of every entry in the pot, each player's id with their exact deposit, sorted so the order cannot be gamed. When the round closes we lock in a future EOS block number and later mix that block's id into the seed. Nobody, us included, knows that block id while the round is still open.
clientSeed = SHA-256( userId:value | userId:value | ... sorted by user ) roll = HMAC_SHA256(serverSeed, clientSeed + ":" + eosBlockId + ":0") ticket = floor(roll * potInCents)
Every cent in the pot is one ticket. The winner is whoever owns the ticket the roll lands on, so your chance is exactly your share of the pot.
Case battles
The client seed is the SHA-256 of every seat in the battle, each player's id with their slot index in order. When the battle fills we lock in a future EOS block number and later mix that block's id into the seed. Each case pull gets its own nonce in round and seat order; jackpot, tiebreak, and Wheel of Fortune modes each consume one additional nonce after the pulls.
clientSeed = SHA-256( userId:slot | userId:slot | ... by seat )
seed = clientSeed + (":" + eosBlockId when recorded)
roll(n) = HMAC_SHA256(serverSeed, seed + ":" + n)
roll = first 8 hex digits / 4294967296
nonce 0 .. rounds×seats−1 case pulls
next nonce if jackpot/tiebreak winner pick
next nonce if Wheel of Fortune payout multiplierWheel of Fortune multiplier odds
Fortune battles pay the winning side a multiplier of the unboxed pot. The multiplier is the first segment whose cumulative chance exceeds the fortune roll (same roll-to-segment mapping as on the battle page).
- 0.2× — 10%
- 0.5× — 21%
- 0.75× — 34%
- 1× — 20%
- 1.5× — 7.0%
- 2× — 5%
- 3× — 2%
- 5× — 0.8%
- 10× — 0.2%
What each value proves
Server seed hash
Published before betting opens. Proves we picked the server seed in advance and never swapped it.
Client seed
Comes from players, not from us. Proves we could not steer the result on our own.
EOS block id
Public entropy from outside the site. Nobody knew it while the round was still open.
Roll
The derived number. Recompute it and it will match the roll recorded against the game.
