For Double, we use two generated seeds: a public and server seed. These seeds are created at the start of each day (00:00 UTC). Both of the seeds are a SHA-256 hash of 16 cryptographically secure random bytes. We use both of the seeds and game id to generate the winning roll number. During this time, the server seed is hashed and displayed in red on the double's history page to ensure transparency without revealing future outcomes. At 00:00 UTC the following day, the hashed server seed used in the previous day is revealed.

Double outcomes are determined by a roll number between 0 and 14, corresponding to the following results:

Cyan: 1, 2, 3, 4, 5, 6, 7

Green: 0

Black: 8, 9, 10, 11, 12, 13, 14

For Crash, we use a sequence of 10 million SHA256 hashes. It starts with an initial server secret that repeatedly gets the SHA256 function applied to itself 10 million times. The game uses these hash values in reverse order to generate crash points. This approach allows anyone to verify the integrity of the entire chain. After each game ends, we publish the hash that was used to determine the game's result. By applying the SHA256 function to any revealed seed, you can obtain the hash of the previous game. This process can be repeated back to the very first game in the sequence, ensuring full transparency and fairness.

For Cases, we use client-server seeding system to generate the final roll result. Check "how it works" for more in depth explanation about the seeds. Before the case opening, we display SHA256 hash of the serverseed to show that we are committed to the server seed. You may set your own client seed to alter the randomness of the outcome. After the case is opened, we display the unhashed serverseed so you can verify the result of your outcome. We use seedrandom function with an input seed: {game}:{serverseed}:{clientseed}:{nonce}, where nonce is the case's index in multi-opens.

For Mines, we use client-server seeding system to generate the final roll result. Check "how it works" for more in depth explanation about the seeds. Before the mines game, we display SHA256 hash of the serverseed to show that we are committed to the server seed. You may set your own client seed to alter the randomness of the outcome. After the mines game ended, we display the unhashed serverseed so you can verify the result of your outcome. We use seedrandom function with an input seed: {game}:{serverseed}:{clientseed}:{nonce}, where nonce is the amount of mines.

For Case Battles, we use a provably fair system where a public seed is not known until after the casebattle starts. We achieve this by committing to an EOS Block that is not yet mined but will be in the near future, and we then use its hash as the public seed. In addition to the public seed, we use a generated server seed that we commit to by displaying the SHA256 hash of it. The individual results are than calculated using seedrandom function with the following formula: {game}:{serverseed}:{publicseed}:{nonce}, where nonce is player's position + round.

In case battles, it's common for players to reach a tie. In such situations, we use an additional floating-point number as a tiebreaker. Each player is assigned an equal segment of the float range, which spans from 0 to 1. The player whose assigned segment where the float falls wins the tiebreaker. to generate this float value we use seedrandom with following function: {game}:{serverseed}:{clientseed}:{nonce}, where nonce is (totalplayers x totalrounds + 1).