Fairness: The most trusted CSGO & CS2 Case unboxing website

case battles verifier

For every battle server seed is generated at the time of creation, then waiting for future EOS Block Id once all slots are filled. Server seed combined with EOS Block Id, slot number and round number use the code to generate 0-9999 tickets (total 10000).

Jackpot mode combines server seed, EOS Block Id and nonce. Use jackpot for jackpot round inside the code.

Verifying Double

At the start of each round server seed is generated and subscription to future EOS Block is made. Round server seed is revealed after round is finished, which combined with EOS Block Id and nonce is used to decide the round outcome using the code.

Case Opening Verifier

For independent verification, you can replicate the results of any round by copying the input and using the provided code.

You must generate a new server seed by changing your client seed before you can verify your rolls using the code above. If the seed is red, that mean it is still hashed and not verifiable.

21 verifier

You can verify the 21 fairness using the code. The deck is shuffled after every round using server seed, client seed and nonce. There are 8 total decks in use.

You must generate a new server seed by changing your client seed before you can verify your rolls using the code above. If the seed is red, that mean it is still hashed and not verifiable.

21 Multi verifier

At the start of each round server seed is generated and subscription to future EOS Block is made. Round server seed is revealed after round is finished. Server seed later is combined with EOS Block Id, nonce and card index to generate one of 52 cards using the code.

21 Multi uses infinite decks.

mines verifier

You can verify the Mines fairness using the code. Use round server and client seeds, nonce, grid size and mines count from your bet history to verify the outcome.

You must generate a new server seed by changing your client seed before you can verify your rolls using the code above. If the seed is red, that mean it is still hashed and not verifiable.

keno verifier

You can verify the Keno fairness using the code. Use round server and client seed, nonce from your bet history to verify the outcome.

You must generate a new server seed by changing your client seed before you can verify your rolls using the code above. If the seed is red, that mean it is still hashed and not verifiable.

hilo verifier

You can verify the Hilo fairness using the code. The deck is shuffled after every round using server seed, client seed and nonce. Game uses infinite decks.

You must generate a new server seed by changing your client seed before you can verify your games using the code above. If the seed is red, that mean it is still hashed and not verifiable.

Limbo/Plinko/Roll Verifier

For independent verification, you can replicate the results of any round by copying the input and using the provided code (Limbo, Plinko, Roll) .

You must generate a new server seed by changing your client seed before you can verify your rolls using the code above. If the seed is red, that mean it is still hashed and not verifiable.

For Plinko, the verification process displays the box number of the win multiplier.

To verify older bets you need to use this link Roll (if bet ID is lower then #36801117).

Example for Plinko:
If the result shows "Box Number: 3", it means the ball landed in the box number 3 from the left (on low risk with 8 rows it would correspond to 1.2x payout).

Coinflip Verifier

Each round generates a server seed, and subscribes to future EOS Block once both participants join. Round server seed, combined with EOS Block Id and round id are used to decide the outcome using the code.

Wheel Verifier

At the start of each round server seed is generated and subscription to future EOS Block is made. Round server seed is revealed after round is finished, which combined with EOS Block Id, nonce and total bets number is used to decide the round outcome using the code.

Raffle Verifier

At the start of each round server seed is generated and subscription to future EOS Block is made. Round server seed is revealed after round is finished, which combined with EOS Block Id, nonce and total bets number is used to decide the round outcome using the code.

crash verifier

At the start of each round server seed is generated and subscription to future EOS Block is made. Round server seed is revealed after round is finished, which combined with EOS Block Id and nonce is used to decide the round outcome using the code.

For old rounds: Anyone can easily verify integrity of the chain. We’re publishing a game’s hash immediately after the game ends. By checking that the SHA256 hash of that game’s hash is the game’s hash of the previous game you can make sure that we were not able to modify the result. You can verify the hash chain using the code.

House Edge

21 Multi: ≈0.5% House Edge21: ≈0.5% House EdgeWheel: 2% House EdgeCoinflip: 2% House EdgeDouble: 2% House EdgeRoll: 4% House EdgeCrash: 4% House EdgeHilo: 4% House EdgeCases: 4-10% House EdgeLimbo: 5% House EdgeKeno: 5% House EdgeMines: 6.5% House EdgePlinko: ≈6.5% House EdgeBait: 6.66% House Edge