Topic: [DoubleDownBTC.com] New Blackjack Game *20% BONUS ON BTC DEPOSITS* (Read 3269 times)

Resolved

Resolved

Future cashouts doesn't help that I've got my last .75 btc in limbo.  This isn't a new issue, coinbase made a post about it yesterday, yet you still are sending cashouts their way. This is new....previously they were all instant. Figures, the time I make a largish deposit and withdraw, therws issues holding it up for hours. If I don't have my btc in next 2 hours and I miss some vets on games I want to put in, I'm going to be very pissed off . 

We have a ticket open with Coinbase, there are multiple transactions held up with them right now.  We cannot cancel the transaction at this point because it's already been accepted, We can process any future cashouts manually until Coinbase gets back in sync with the rest of the blockchain.

Do not deposit here, until they fix their cashing put issues.  I've been waiting almost 8 hours, for a withdraw. They have offered zero assistance, have not contacted their cashout provider coinbbase, nothing.

Still haven't gotten my btc. You guys need to contact coinbase or something. Its going on 7 hours now....no reason I should be without my btc this long.

Ok cool no rush. Just making sure it got sent. Can I have the 20% added to acct I played on?

It looks like your transaction is still queued with Coinbase:

https://coinbase.com/network/transactions/d86482b91c946ddcfcc9e1be26761da09788f088a6bd817098ef1b5de37ca9a5

They seem to be taking awhile this morning.  We're thinking of putting a transaction history page on the site so you can track the txn's in and out.  I agree, it's never fun to wonder if your transaction disappeared.

I withdrew .7+ thisorning, never got it...1DoNkCTUZKN9cmBf36uScwEEs74Zfev4ue is the address I withdrew to....

Credit was sent back in txn Hash   fe751d7a34bd0479078e4f043c57a6f17d82ad92393f2c4d6a22dc847d334165

I'm really concerned that you keep having these issues.  I've investigated the transaction and it doesn't look like it's been picked up by Coinbase yet.  The transaction you referenced is in block 260089, but coinbase, who we have been using as a temporary deposit processor since last weekend, is only reporting up to block 260029.  There seems to be a serious lag right now.

We moved to coinbase temporarily as a way to expedite deposits and confirmation verifications, this seems to be causing different issues.

Our developer is investigating an option to use our previous bitcoind solution. It doesn't look like there is a reliable thirdparty processor yet unfortunately.

We find it hilarious that you speak of "a further level of trust" when you have blatantly stolen our HTML, CSS, Javascript, art and sound files, and claim provably fair blackjack yet actually have no such thing. The fact that you think any of this is OK is mind boggling.

We have worked hard to create a casino that is trustworthy and fun to play. We will continue to improve our site, and we hope that in the end, users will know which web sites they can trust their Bitcoins with.

Excellent catch.  Thanks for reporting that.  You are correct, the check logic in the JS is disabled, this seems to be a missed relic from testing.  The code is being corrected today. 

As for how we calculate the deck from the game seed:
It's pretty straight forward
We take the final game seed + the game seed hash, convert this to a string (which is a byte stream in PHP) and use it as the seed for the mt_srand function in PHP. This will seed the Mersenne Twister algorithm. We then perform a Fisher Yates shuffle on the shuffled deck, using the mt_rand function as the RNG. This adds two levels of randomness to the shuffle and provides a reproducible result after the fact.

In the essence of transparency we've decided to add a feature to the site which will allow anyone to download a public game history file each day which will show all games played, the server, client and game seed as well as the complete shuffled deck. This can be used to perform analysis on the dataset, or simply to verify a particular game again after the fact.

We are also in the processes of having our game engine externally audited which will add a further level of trust to our engine.

While I am happy that a developer let this test get into production, I can assure you that the games are random. Anyone that has a particular concern about the outcome of a game or the randomness of a shuffle, please contact any of us directly and we will provide the complete audit history of any game.

Thanks again for the great bug catch.

We have performed an analysis of the provably fair code on DoubleDownBTC and believe that it is not legitimate. There is absolutely no guarantee that the shuffle generated is random, so they could be packing the deck in their favor.

Using the values from the provably fair dialog, when we try to manually generate the deck given the game seed, we get a different deck of cards. This means that on the server side it is not actually using this verification data. We suspect that the server is not following the rules of provably fair and is shuffling the deck however it wants.

GameID: 523d3d4915413651609f8cbf
Game Seed == Server Seed + Client Seed:
14593047563445106624089340932
Mersenne(Game Seed) == Final shuffled deck (first 52 cards):
kd8hjhah4d3c9c6h9hkskcjc7djdah7sahtdtc8c3hjd4skh2c2d

Can you please demonstrate how you were able to generate that deck of cards given that game seed?

The client-side Javascript function that verifies the deck shuffle has been purposely disabled. The function is called check_game(), and it is supposed to check that the deck that was actually played is the same as what the server committed to when it initially sent the server seed. However, after this function shuffles the deck, it then just cheats and manually sets the generated deck of cards to what the server dealt:

var game_cards = game_info_package.deal_hash_source.slice(1, first_close_paren);
check_cards_string = game_cards;
if (check_cards_string == game_cards) {
    proves_deck = true;

Essentially the code is generating the deck, but then setting check_cards_string to equal game_cards, so that the test will always pass. This means that the verify dialog will falsely tell you that the shuffle was legitimate, when it in fact was not.

To summarize, the server is not shuffling the deck in a provably fair way. The client code has been purposely disabled to not point out this error. Please be careful. We don’t want people getting scammed betting with their Bitcoins, especially on a site that looks almost identical to Bitcoin Video Casino.

But....

your site looks exactly like the video blackjack machines at every casino near me....

So......

Didn't you copy from THOSE COMAPNIES first?

They copied our CSS, Javacript and HTML without our permission.

Refunded. 

We just stopped using the blockchain.info API to confirm transactions until whatever is wrong with their system is fixed.  If anyone else feels that a deposit hasn't credited, please drop me a note and I'll get it resolved.

Thanks!

Thanks, our payout percentage was calculated using the wizard of odds calculator which gives us a house edge of 0.42945% which is technically 99.57055%  We rounded to 99.6, but it's a good point. The site has already been updated to be more accurate.

As for the deposit, let me know the BTC address and I'll investigate.  We use the blockchain.info API to verify confirmations.  There's been some weird problems with their service over the last 24 hours and we've seen a few transactions that aren't showing as confirmed even though they are.  We're going to be manually watching the queue until blockchain.info gets sorted out.

We're flattered that you thought our casino was great enough to copy.

That being said, we always recommend that the community be diligent about the casinos they play on. We found that your stated return to player is 99.6%, but with the BJ rules we used (which you didn't change) the return to player is 99.5%. Our 99.6% comes from a .1% contribution to the progressive jackpot. You have no progressive jackpot, so where is that extra .1% going?

We also tried playing on your site but the deposit was never credited.

It looks like our deposit queue got a little backed up (a good problem to have I guess), the transaction finally processed and there was nothing wrong with your account so you can keep using the same one. We've added another worker to our deposit process and the queue is back down to zero. Transactions should be posting instantly again. Sorry for the hassle with the long deposit delays!