3. Your slogan Hack us you mean you're pretty sure your code is secured, but why you still faced a vulnerability in your casino?
OK that's like putting a huge bullseye for hackers on your casino.
Just for information you can use this sites
https://www.toolsley.com/hash.html to validate the cards hash, just copy the deck cards and you will see an exact hash on SHA256 to validate.
I would host this locally if it's even possible, because as I mentioned in a previous post, DNS hijacking is a real thing and can send back different validations or even hashes. Do not make a network request to that resource in production.
@roynx98
I noticed you posted a 50 bits promo code here just now but removed it. I'm the one that used it (I think they're still one-time use?).
I wanted to see how your bankroll would withstand a few bets so I was gambling 10 bits at a time for most hands.
As I expected, I eventually lost all that bonus money after going as high as 110 bits at one point. So it at least makes me feel better that you have some kind of house edge.
I'm not too comfortable that you set the Blackjack payout to 30 bits. I know it's rare, and a streak of losing (as in theoretically impossible to win) hands swallowed all those bits - including a 50bits bet I placed towards the end of the run after a series of 10 bits, but consider the possibility of someone striking lucky and hits blackjack getting the triple payout and immediately withdrawing.
Given that 50bits is the max bet, a 150bits win can still punch a huge hole in your [now depleted] bankroll.
Mmm, the cards are picked randomly, any ideas of how demonstrate that the house does not have any edge