bustabit.com -- The Social Gambling Game

[rcoins0720]

can give some to try??
1C7VMBwL1DEnxGvEE9zPWkUgK4QiT6QrS8

my id is williamho

There's a builtin faucet, that gives out 2/bits an hour -- which is enough to play at the 1 bit table for a while =)

the chances rather are very small

[yudkowske]

Are there any withdrawal limits on this website?

[poordeveloper]

At the footer of your site it says "Bustabit.com is fully owned and operated by MoneyPot S.R.L. a Costa Rican gaming company (License No. 3-102-700828)"

I guess you haven't updated that information yet?

[devans]

Are there any withdrawal limits on this website?

You can't withdraw more than your balance, obviously. Otherwise there aren't any limits or restrictions.

[yudkowske]

Are there any withdrawal limits on this website?

You can't withdraw more than your balance, obviously. Otherwise there aren't any limits or restrictions.

Haha yeah but what i'm asking for is does this website have any issues with withdrawals? Some casino sites delay withdrawals or deny to make it at all, especially large sum (10btc+) that's why i'm concerned.

[DarkStar_]

Are there any withdrawal limits on this website?

You can't withdraw more than your balance, obviously. Otherwise there aren't any limits or restrictions.

Haha yeah but what i'm asking for is does this website have any issues with withdrawals? Some casino sites delay withdrawals or deny to make it at all, especially large sum (10btc+) that's why i'm concerned.

No. Bustabit has had some very large withdraws take place as they have quite a few whales, and IIRC no one has ever had to wait days to get withdraws. There's people with over 100 BTC profit and none of them have complained.

[yudkowske]

No. Bustabit has had some very large withdraws take place as they have quite a few whales, and IIRC no one has ever had to wait days to get withdraws. There's people with over 100 BTC profit and none of them have complained.

I hope that's true. At the moment i'm waiting for my withdrawal for over an hour already and it still has 0 confirmations.

[poordeveloper]

No. Bustabit has had some very large withdraws take place as they have quite a few whales, and IIRC no one has ever had to wait days to get withdraws. There's people with over 100 BTC profit and none of them have complained.

I hope that's true. At the moment i'm waiting for my withdrawal for over an hour already and it still has 0 confirmations.

When you say it still has 0 confirmations, I assume the transaction has been sent, right?

Neither Bustabit nor any other Bitcoin site (provided they don't send with a low fee on purpose) can guarantee fast Bitcoin confirmations. It's up to the Bitcoin network (the miners, actually) to choose the transactions which will be confirmed (included in a block) and when.

So Bustabit has already paid you, you just haven't received it yet

[yudkowske]

So Bustabit has already paid you, you just haven't received it yet

They should add an option for people to pay higher fees in case they want their transactions to be processed quicker.

[yudkowske]

But fortunately the next release will be a lot better at this, and there will be two different withdrawal speeds to strike a better balance

Sounds good, thanks for the info. May i ask what was the largest withdrawal made on your website? I see people with 80+ btc on their balance (net profit) in the leaderboard. Wondering why are they still holding and if it's even real

Couple of questions:
1. Do you ask for any verifications when withdrawing the large sums?
2. Am i able to have multiple accounts to test different strategies?

[yudkowske]

Yeah, that's fine

Awesome! I'm about to deposit 1 btc to test the water
May the luck be with me.

[KloNEM]

Hi Ryan,

could you please think about (at least temporarily) lowering the withdrawal fee ? In the last days, BTC fee level has been clearly decreased, so I think that 700bits is unnecesarily high fee now. I guess lowering into ~ 400bits would be more than enough. Thanks.

[actmyname]

Hi Ryan,

could you please think about (at least temporarily) lowering the withdrawal fee ? In the last days, BTC fee level has been clearly decreased, so I think that 700bits is unnecesarily high fee now. I guess lowering into ~ 400bits would be more than enough. Thanks.

Taken from estimatefee stats: For a standard transaction with 3 inputs and 2 outputs (this is being very generous) to confirm within ≤2 blocks, since the size is 522 bytes and the fee 136 sat/byte it is around 700 bits.

[game-protect]

WARNING!

There still is no governmental or regulatory framework governing online gambling or eGaming whatsoever, as such no official Costa Rica Online Gambling License designed to deal with e-gaming (gambling over the Internet) exists.

The absence of legislation governing online gambling operations or administration from Costa Rica means very clearly that a Costa Rica Online Gambling License does NOT exist!

As no special Costa Rica Online Gambling License exists or is required in Costa Rica, the business is operated by a specifically registered Costa Rican Company.

This provides for all the profits from the company to be tax free and indemnifies the directors from liability!

[dogevisitor]

Hi Ryan,

could you please think about (at least temporarily) lowering the withdrawal fee ? In the last days, BTC fee level has been clearly decreased, so I think that 700bits is unnecesarily high fee now. I guess lowering into ~ 400bits would be more than enough. Thanks.

Sorry about that, yeah it definitely should be lower. I made the mistake of hard-coding that value into the configuration file, with the only way of changing it reset the web-server. Which wouldn't be so bad, except I also made the mistake of storing mutes in memory 

So I've dropped the withdrawal fee now, but it won't kick in until I reset the webserver (when ever that is).

Fortunately in the next release (which is getting very close!) both of those issues are fixed, and withdrawals are going to be way cheaper. Like crazy cheap (thanks to me spending over a month optimizing coin selection and partial batching and what not ).

Have you ever considered actually opening a true wallet service?

[dogevisitor]

Have you ever considered actually opening a true wallet service?

Yeah. I actually have all the pieces that could make a really kick-ass wallet service (at least if you care about fees and on-chain privacy). The main problem is just that I'm really constrained for time. I'm already pretty delayed for bustabitv2 (I really wanted it out 6 months ago), no small part because of side-tracking with stuff like integrating a constraint-solver for handling withdrawals in a privacy/fee maximizing way

But if after the bustabitv2 launch everything is going smooth, I might split out the code to make a special wallet service =)

You need to hire an assistant haha, or a team

[KloNEM]

Hi Ryan,

could you please think about (at least temporarily) lowering the withdrawal fee ? In the last days, BTC fee level has been clearly decreased, so I think that 700bits is unnecesarily high fee now. I guess lowering into ~ 400bits would be more than enough. Thanks.

Sorry about that, yeah it definitely should be lower. I made the mistake of hard-coding that value into the configuration file, with the only way of changing it reset the web-server. Which wouldn't be so bad, except I also made the mistake of storing mutes in memory 

So I've dropped the withdrawal fee now, but it won't kick in until I reset the webserver (when ever that is).

Fortunately in the next release (which is getting very close!) both of those issues are fixed, and withdrawals are going to be way cheaper. Like crazy cheap (thanks to me spending over a month optimizing coin selection and partial batching and what not ).

Yeah, I absolutely understand to you with that hard-coding mistake, I did it the same many times in my "IT life" .

Which is just interesting now for me -- the fee on the blockchain is already lowered (around 157bits), although it is still cutting 700bits from Bustabit account by withdrawal. I supposed that "700 hardcoded bits" will be still used within  the BTC transaction (until you'll restart the server) ?

[TwitchySeal]

So thanks to the extensive research of vadoff, you can see potentially manipulated results from (7mbtc.com) in purple:
https://jsfiddle.net/vadoff/r4kp44Lv/1/embedded/result/

I can't come up with a good explanation for how this would be happening, and it means their house edge isn't matching what they are advertising. I will update the bustabit.com/license.txt file to reference this post

So they are only manipulating winning bets by paying out less than they should?

If I were a cheater that owned a site like this, that's what I would do.  Players are much less likely to scrutinize a winning bet.

Does 7mbit.com have any presence on this forum?

[DarkDays]

So thanks to the extensive research of vadoff, you can see potentially manipulated results from (7mbtc.com) in purple:
https://jsfiddle.net/vadoff/r4kp44Lv/1/embedded/result/

I can't come up with a good explanation for how this would be happening, and it means their house edge isn't matching what they are advertising. I will update the bustabit.com/license.txt file to reference this post

So they are only manipulating winning bets by paying out less than they should?

If I were a cheater that owned a site like this, that's what I would do.  Players are much less likely to scrutinize a winning bet.

Does 7mbit.com have any presence on this forum?

Maybe I'm reading it wrong, but it looks like they are saying that some games are crashing at very low numbers (which would make most if not all players lose when some of them would have won) when they should be crashing at higher numbers.  For example:

27807ebb19abb46b215a159430ec701b1ff062867b9458eef139bb782f4c8536   should have crashed at 1.13   but crashed at 1.10

eb18dca6fa47714a37f95622a760a8a87061b48b80da3c9f5b2c64bd26baf566   should have crashed at 1.43   but crashed at 1.01

d1a0c7681205d1150beb27fa36f0062999d0fbb87fc2e160e43aae30500a35d6   should have crashed at 1.48   but crashed at 1.02

8887f6e956118c1625878bb46d2754c03f3983dd6f11a33d44537e9e8028f9a9   should have crashed at 1.63   but crashed at 1.00

0aea96252b1f5a6b72672a8930006c9d62e4dd67e2a9dc1933797b5629ab231a   should have crashed at 1.66   but crashed at 1.01

9f01292ec66a211bd09bdfeb744392b3ccf43d70fd2b8d7c3e1bfb4a20fb097a   should have crashed at 1.21   but crashed at 1.08

e97d35503abc8f9480226e6192efaf7780982e0ad04e553858ffef7d085774bb   should have crashed at 1.90   but crashed at 1.09

[TwitchySeal]

So thanks to the extensive research of vadoff, you can see potentially manipulated results from (7mbtc.com) in purple:
https://jsfiddle.net/vadoff/r4kp44Lv/1/embedded/result/

I can't come up with a good explanation for how this would be happening, and it means their house edge isn't matching what they are advertising. I will update the bustabit.com/license.txt file to reference this post

So they are only manipulating winning bets by paying out less than they should?

If I were a cheater that owned a site like this, that's what I would do.  Players are much less likely to scrutinize a winning bet.

Does 7mbit.com have any presence on this forum?

Maybe I'm reading it wrong, but it looks like they are saying that some games are crashing at very low numbers (which would make most if not all players lose when some of them would have won) when they should be crashing at higher numbers.  For example:

27807ebb19abb46b215a159430ec701b1ff062867b9458eef139bb782f4c8536   should have crashed at 1.13   but crashed at 1.10

eb18dca6fa47714a37f95622a760a8a87061b48b80da3c9f5b2c64bd26baf566   should have crashed at 1.43   but crashed at 1.01

d1a0c7681205d1150beb27fa36f0062999d0fbb87fc2e160e43aae30500a35d6   should have crashed at 1.48   but crashed at 1.02

8887f6e956118c1625878bb46d2754c03f3983dd6f11a33d44537e9e8028f9a9   should have crashed at 1.63   but crashed at 1.00

0aea96252b1f5a6b72672a8930006c9d62e4dd67e2a9dc1933797b5629ab231a   should have crashed at 1.66   but crashed at 1.01

9f01292ec66a211bd09bdfeb744392b3ccf43d70fd2b8d7c3e1bfb4a20fb097a   should have crashed at 1.21   but crashed at 1.08

e97d35503abc8f9480226e6192efaf7780982e0ad04e553858ffef7d085774bb   should have crashed at 1.90   but crashed at 1.09

Ahh, that makes sense.  I was totally wrong - clearly a Bustabit n00b