Blackjack Provably Fair

Our game is built in a way that allows you to verify it's fair.

Just head to your account page and you'll find all your hands listed, you'll be able to see the order of the shuffle cards and the public and private hashes for a given round.

Don't forget you need to use the cards on the order they were shuffled, before they were cut!

On the middle of the game screen, and at every hand, you'll find an hand identifier you can easily randomize, everytime you randomize you get a new set of shuffled cards and, therefore, a new hand hash.

The hand hash is generated by md5'ing a concatenated round secret, the ":" character and all the cards on their shuffled order. So if you want to generate your own hand hash you would be md5'ing something in the format "secrethash:2♥J♦J♥A♥4♣..."

You can use the calculator bellow to generate the hand has using the hand secret and cards in their shuffle order, it runs completely on the client-side and it's developer friendly, since all the code is inline (function generateHandHash).

So, just copy and paste your hand secret hash and cards (make sure there are no spaces on the beginning, middle or end of the text), generate an hand hash with the tool bellow and compare it against the original hand hash - and you'll see we're completely fair, trustable and safe to use.

Cut the deck

The provably fair system proves that the card order cannot be changed since even before the bet has been placed.
To assure players that the system is using a truely random and doesn't draws pre-determined hands we allow users to cut the deck

By cutting the deck you can be 100% sure that our randomization is 100% fair.

You get to select the exact card where you want to cut the deck, this means that we will 'cut the deck' at that card, by moving the cards before the one you select (excluding the selected card) to the end of the deck.

This happens after the cards were already selected and the hash shown to you, on a stage where the server is not able to change them (as explained on our provably fair page) therefore proving that the system is 100% random, fair and trustworthy.

With this feature you can rest assure that the random is fair since the server will never be able to know upfront what cards will belong to you or the dealer - since when you define the card where the deck is cut it changes everything.

Instead of defining a cut card every single hand you can opt by using a random one, this random number is generated by your browser (developers may look for this random in our source code, it's using the system Math.random at every new hand generated and is never sent to the server) and you can change it at any time before placing the bet (this is activated by default).

All the round information will be available for 3 months and then erased.

Roulette Provably Fair

Our game is built in a way that allows you to verify it's fair.

Just head to your account page and you'll find all your spins listed, you'll be able to see the random number picked and the public and private hashes for a given round.

On the top left of the game screen, and at every spin, you'll find an spin identifier you can easily randomize, everytime you randomize you get a new random number, therefore, a new spin hash.

The spin hash is generated by md5'ing a concatenated round secret, the ":" character and the random number. So if you want to generate your own spin hash you would be md5'ing something in the format "secrethash:28" (if 28 was the picked number).

You can use the calculator bellow to generate the spin hash using the spin secret and number, it runs completely on the client-side and it's developer friendly, since all the code is inline (function generateSpinHash).

So, just copy and paste your spin secret hash and number (make sure there are no spaces on the beginning, middle or end of the text), generate an spin hash with the tool bellow and compare it against the original spin hash - and you'll see we're completely fair, trustable and safe to use.

All the round information will be available for 3 months and then erased.

GabeN's Deal Provably Fair

Our game is built in a way that allows you to verify it's fair.

Just head to your account page and you'll find all your games listed, you'll be able to see the order of the shuffle cases and the public and private hashes for a given round.

Don't forget you need to use the cases on the order they were shuffled, before they were cut!

On the middle of the game screen, and at every game, you'll find an game identifier you can easily randomize, everytime you randomize you get a new set of shuffled cases and, therefore, a new game hash.

The game hash is generated by md5'ing a concatenated round secret, the ":" character and all the cases on their shuffled order. So if you want to generate your own game hash you would be md5'ing something in the format "secrethash:2-4-6-8..."

Note that each case is represented by the number of percentage that it awards as prize, so 2 would be 2% and 1000 would be 1000% of the game bet (so, on a $1 bet, 2 would mean the $0.02 case and 1000 the $10 case).

You can use the calculator bellow to generate the game has using the game secret and cases in their shuffle order, it runs completely on the client-side and it's developer friendly, since all the code is inline (function generateGameHash).

So, just copy and paste your game secret hash and cases (make sure there are no spaces on the beginning, middle or end of the text), generate an game hash with the tool bellow and compare it against the original game hash - and you'll see we're completely fair, trustable and safe to use.

Cut the order

The provably fair system proves that the case order cannot be changed since even before the bet has been placed.
To assure players that the system is using a truely random and doesn't draws pre-determined games we allow users to cut the order

By cutting the order you can be 100% sure that our randomization is 100% fair.

You get to select the exact case where you want to cut the order, this means that we will 'cut the order' at that case, by moving the cases before the one you select (including the selected case) to the end of the order.

This happens after the cases were already selected and the hash shown to you, on a stage where the server is not able to change them (as explained on our provably fair page) therefore proving that the system is 100% random, fair and trustworthy.

With this feature you can rest assure that the random is fair since the server will never be able to know upfront what cases will belong to you or the dealer - since when you define the case where the order is cut it changes everything.

Instead of defining a cut case every single game you can opt by using a random one, this random number is generated by your browser (developers may look for this random in our source code, it's using the system Math.random at every new game generated and is never sent to the server) and you can change it at any time before placing the bet (this is activated by default).

All the round information will be available for 3 months and then erased.

Heads or Tails Provably Fair

Our game is built in a way that allows you to verify it's fair.

Just head to your account page and you'll find all your coins listed, you'll be able to see the order of the shuffle number and the public and private hashes for a given round.

On the middle of the game screen, and at every toss, you'll find an coin identifier you can easily randomize, everytime you randomize you get a new random number and, therefore, a new coin hash.

The coin hash is generated by md5'ing a concatenated round secret, the ":" character and the number generated for the given toss. So if you want to generate your own coin hash you would be md5'ing something in the format "secrethash:94"

You can use the calculator bellow to generate the coin hash using the coin secret and number in their shuffle order, it runs completely on the client-side and it's developer friendly, since all the code is inline (function generateCoinHash).

So, just copy and paste your coin secret hash and number (make sure there are no spaces on the beginning, middle or end of the text), generate an coin hash with the tool bellow and compare it against the original coin hash - and you'll see we're completely fair, trustable and safe to use.

Remember:

  • The server will generate a number, from 1 to 100.
  • If the number is equal or lower than 47, the coin result is "CT" (Head).
  • If the number is great than 47 and equal or lower than 94, the coin result is "T" (Tail).

All the round information will be available for 3 months and then erased.

Defuse Provably Fair

Our game is built in a way that allows you to verify it's fair.

Just head to your account page and you'll find all your bombs listed, you'll be able to see the order of the shuffle number and the public and private hashes for a given round.

On the middle of the game screen, and at every defuse, you'll find a bomb identifier you can easily randomize, everytime you randomize you get a new random code and, therefore, a new bomb hash.

The bomb hash is generated by md5'ing a concatenated round secret, the ":" character and the code generated for the given bomb. So if you want to generate your own bomb hash you would be md5'ing something in the format "secrethash:94"

You can use the calculator bellow to generate the bomb hash using the bomb secret and code in their order, it runs completely on the client-side and it's developer friendly, since all the code is inline (function generateCoinHash).

So, just copy and paste your bomb secret hash and number (make sure there are no spaces on the beginning, middle or end of the text), generate an bomb hash with the tool bellow and compare it against the original bomb hash - and you'll see we're completely fair, trustable and safe to use.

Remember:

  • The server will generate a number, from 0 to 9999.
  • If the number under 4 characters we'll add a zero for each missing character (so 0 becomes 0000, 1 becomes 0001, etc).

All the round information will be available for 3 months and then erased.