OMG yeah I didn't think of that: if someone mixed up their withdraw with the miner fee box and sent a miner several hundred dollars for a few cents worth of bitcoin, yeah that would seriously suck LOL. So, yeah, no... never mind my idea. Bad idea. LOL
Honestly I play so fast I can't remember hardly any individual hand after a few seconds, LOL
But looking at the screen shot I saved of the error dialog box, I think we can see that the dealer had a hard 17 there and my hand (with 8 chips bet) consists of four cards. I don't know what the cards were exactly but clearly ONE of the cards is missing from by browser's understanding of the hand dealt!
If starting hand was A-5 vs dealer 17 that's a hit of course. 6/16 plus the next (?) card of 7 makes it hard 13 vs 17 so I'd have HIT again: if I then got another Ace it's only 14 vs 17 *SO* yes I WOULD have HIT again (to presumably get that KING and bust out at 24) but since we can see there that my hand only shows FOUR cards, it appears the browser thinks I stood on 14 versus dealer 17??
Either way I would have lost the hand (bust out or 14 loss to hard 17) so regardless it's a correct result that my 8 chips bet was lost.
But it's very strange (and a little worrisome) that the server and my browser could have "LOST" a card here.
IF this was a big bet and/or IF it was a lost card that'd make the house win versus player win, THAT is potentially a big problem
P.S. Thanks for upping the fee for us, hopefully temporarily, to help the slow transaction clearing problem. Nice of you
Hehe yeah maybe we'll hold off on the extra miner's fee field for now.
Yes it's very strange that the number of cards that your browser is showing is different than what the server thinks. It certainly makes sense that you would have hit on 14 when the dealer shows 17, so for some reason your browser does not show that final card that you hit.
As part of our provably fair system, we sanity check variables on the client and server side to make sure everything is consistent. This has helped us uncover a few bugs during development in addition to proving that our games are fair and completely random. Fortunately if a user were playing a big hand he would see this dialog box and could then contact us to claim his winnings.
We've tried to reproduce this bug by autoplaying games on a development server for days on end without any luck. Bitcoin Video Casino has been around for 2.5 years now and this is now the second time we've heard about this bug. The other user had the same issue -- the number of hits on the server was not the same as the client. I wonder if some kind of network issue is causing things to get out of sync? That might explain why we can't reproduce this locally. We will try to take another look at the client code. I really would love to fix this super rare issue but if we can't reproduce it we don't really know where to look...
Thanks for letting us know about this issue.
If you PM me your Bitcoin address I will refund your game and send you some extra coins for your troubles.
Poll
