I am interested in this crowd sale. Will there be any platform where people can trade these tokens freely?
I hope these tokens can be like Ethereum where there is a wallet and exchanges.
Yeah, I'll build a simple exchange into bustabit in order to buy/sell/transfer tokens. If there's a half-decent OpenAssets exchange, I'll allow people to withdraw the tokens as OpenAssets where you do can trade them there too |
|
|
|
I was going to do the same thing with BetKing.io months back but it would have actually been illegal to do so in the UK.
What about the current bankroll investing you have? And if that's legal, what if you pay company expenses out of the bankroll? And if that's legal, what if you stop accepting new investors? And if that's legal, what if you allow people to transfer their bankroll stake to other people? And if that's legal, it's pretty much the same as bustabit's crowd fund  |
|
|
|
Hi Ryan
Can you give us some information on the legality of this and in what country?
I've intentionally tried to keep it as informal-ish as possible, and try avoid it being a clear security. The actual company I run is incorporated in Costa Rica, but there it's more just a grey zone where a lot of stuff is legal by the fact it's not illegal. I'm offering a stake in the (net) liquid assets, as opposed to the company it itself, but my real primary goal here is just to not misrepresent anything or piss anyone off. As I no longer live in the United States (nor ever was a citizen), I don't believe I fall under the jurisdiction of the SEC or what not. |
|
|
|
If you'll be withdrawing your own funds from the bankroll to replace them with crowd funded coins, wouldn't that effectively erase your incentives not to cheat? Since you know the seed you could look ahead at the games to come and slowly draw from the bankroll whenever you please.
Yeah, for all intents and purposes investors will be totally at my mercy Dont go for Montenegro licence
Any reason why? |
|
|
|
Indeed, how are the dividends structured?
Like, when are they paid?
In bits, or in BTC's?
bits are just a millionth of a bitcoin, so it's the same thing  But dividends will be paid into the current token holders bustabit account When all tokens sold, do tokens have an expiry date or are dividends lifetime of the site?
They don't expire, but will be transferrable Also, 3.000 BTC is quite an amount to raise in only 14 days. My best guess that's related due to the upcoming halving, but perhaps extending the period might be something to re-think.
Also, if the main point is to raise funds, I do not see the benefit of hiding the remaining amount of tokens to be hidden due to sniping.
The main point of hiding the amount of remaining tokens, is just to prevent a vicious cycle of people not investing because they want to wait to make sure the crowd fund looks to be successful. Perhaps I'm being overly cautious and it's a bad idea. But once the crowd sale is over, I'll start providing proof of assets and proof of liabilities so you can verify the amount of tokens wasn't oversold, and what not. |
|
|
|
2. The attack is able to bypass cloudflare which makes me think this are botnets.
3. The attack uses multiple ip ranges, which make it hard to ban all of it.
If the attack isn't showing in cloudflare, it means they have your ip address. If they have your ip address, there is no way you will be able to stop the attack, even firewalls will be completely useless (what they did to BaB was DDoS using spoofed syn packets with cloudflare ip addresses, which allow it to bypass the firewalls) and once it hits a single machine, it will overload it in sheer volume. The only defense that is going to work is obscurity. You need to change your ip address, and then completely hide it, make sure there's no way for the attacker to know what it is. Make sure that you don't have any DNS entries pointing to the real server etc. If the attacker doesn't know your real ip address, then they'll be forced to go a) Go through CF b) by a layer 7 attack. (Also, ignore the idiots who tell you about "CloudFlare resolvers" and what not, if you configure the service right no one can find your ip address. I for a long time had a 1 BTC open bounty on anyone who could name a bustabit ip address, and it was never claimed) |
|
|
|
I read about the dividends, when are those paid?
No fixed time, just when ever the site wants to distribute its money or feels like it has too much money in idle assets |
|
|
|
I have a question regarding that token these will be trade-able right after crowd sale or these will will be similar to an invest which we make into casino bankroll, you have any plan to run social media, signature bounties to catch attention of other people.
Yeah, pretty soon after the crowd-sale you'll be able to transfer and/or sell tokens to other users. Ideally the tokens will be withdrawal-able in the form of OpenAssets tokens (i.e. so you can use a colored coin wallet to manage them) but unless someone builds a secondary market for OpenAssets there's not really much point Looks good.
Only thing I wouldn't do is that "gambling loan platform". Gamblers and loans just don't go well together (I actually have been actively loaning on seals in '13 to only very specific people whose identity I knew, but still it's a losing game.) As website I wouldn't actively participate in that. But I can imagine it's just 1 of the many ideas you have.
The site itself is definitely not going to loan money -- but like you, people *already* are doing lots of gambling loans. So instead of sending them money and hoping they follow the conditions of the loan, I was planning on building proper support for some of the common loan types. e.g. So you can send someone X BTC loan, and they need to repay Y BTC in loan. Until the loan is repaid, they can not withdraw and their profile shows they have an outstanding loan. So the site itself won't take any risk, just give people better tools to do what they're already doing |
|
|
|
Bustabit is one of the most popular bitcoin gambling sites (probably second only to primedice, at least by amount wagered), and today I'm announcing that it's going up for crowd sale. To avoid repeating myself too much, I'll just post the link to the full details are here: https://www.bustabit.com/crowdsaleComments, criticisms and questions are welcome! |
|
|
|
As most of you here know, bustabit is one of the most popular bitcoin gambling sites (probably second only to primedice). Well I'm happy to announce that it is going up for crowd sale! To avoid repeating myself too much here, I'll just post the link to the full details are here: https://www.bustabit.com/crowdsaleComments, criticisms and questions are welcome! |
|
|
|
FUCKING MONEYPOT TEAM. WHERE IS MY MONEY? CANT GET TO SITE, CANT WITHDRAWAL BTC. FUCKING SCAMMERS. ROT IT HELL!
Relax dude, you can be sure that the moneypot team wants to get their site back online even more than you do. Some of these DDoS's are ridiculously painful to deal with. At one point when my site was getting attacked, I had exceeded the CF max-ip-address ban limit and still couldn't cope with the load. (It's not like you can use iptables to help, because the traffic's ip is now from CF). When ever I'm under DDoS, it feels like the whole internet is fundamentally broken and you have to on 3rd party MITMs like CF (who probably are the NSA for what my luck is ) Just cut them some slack and give them a day or two to get back. Even some major brands and exchanges have had a lot of trouble keeping uptime while under attack |
|
|
|
That is why (as stated in the part you quoted) we will be fixing it shortly, either through the launch of v2.0 (which is coming soon) or a patch for it if v2.0 runs into any issues during final testing.
Understood. I just meant that it seems like a sufficiently serious bug that it's worth patching immediately even at the expense of performance. For all intents and purposes while the bug exists, the casino isn't provably fair. As no one can distinguish "invalid hash" from a legitimate db issue to you not wanting to honor the bet (.e.g. a winning bet at the end of a martingale sequence). From the sound of the description of the bug it just sounds like the code is (psuedo code): var hash = getNewHash();
db.queryPromise('INSERT INTO hashes VALUES($1)', [hash]);
this.body = hash;
and needs only needs a 1 line change to: var hash = getNewHash();
yield db.queryPromise('INSERT INTO hashes VALUES($1)', [hash]);
this.body = hash;
(or something?) Or perhaps more likely, I completely misunderstood the problem and I apologize |
|
|
|
|
The problem with skill games that are against the house, is that the odds need to work so that the house can not-lose to expert-level players (or sufficiently advanced bots). At that point everyone who's not an expert-level player (or sufficiently advanced bot) will just get raped. So the only way to fix that is making it fully random so everyone has good odds (e.g. 1% house edge) and then at that point it's just a dice-skin
|
|
|
|
But due to high traffic volume of bets, the database tends slow down even after the dead row limit is met, making the generation and saving of the next hash is slower than the speed of your next bet. So in short the second bet was sent before the next_hash has been properly saved to the database thus giving you the INVALID_HASH error as it cannot find the hash.
V2 should resolve this issue, but since then, ill try to find time (very busy with v2) to look into finding a fix for this for the mean time.
That actually seems like a serious problem, as it would affect the provably fair. Every time a user gets "INVALID_HASH" that's pretty much the same as the bet not validating. It might slow it down slightly sending the hash *after* the database transaction has been `COMMIT`ed but correctness is far more important than speed. (And if speed is important, you could use a pre-generated pool of hashes I guess) |
|
|
|
How is this following the 1% house edge rule? I don't get the maths behind it.
House edge of 1% means that on average you will lose 1% of what you wager. So your expected loss by betting 1 BTC on this bet, is -0.01 BTC (same as any other multiplier). The only real difference here is you're effectively paying 0.01 BTC (amortized) for a (large) shot at winning 1.0102x BTC (or what ever). That's why cowbay (he was the first?) to call it the suckers bet. It seems good, but it's a *fantastic* deal for the casino and a terrible deal for players. If you're interested in maths, check out the FAQ of bustabit it documents it a fair bit and we don't use a traditional "house edge" precisely to make it more fair for players who are doing these types of bets. (For instance, if you bet on bustabit @ 1.01x, you'll be paying a mere 0.009900990099% house edge, precisely because the house has so little risk) . |
|
|
|
The same can be said for most of the bitcoin exchanges and some of them handle missions of $$ per day.
No, that's not the case. Bitcoin exchanges are provably fair by default. I mean, if I deposit $1000 to bitstamp and they only give me $500, then I know I was ripped off. Hence it's provably fair. With your site, I have no way of knowing if I got ripped off, which is what makes it not provably fair. The advice I give to people wrt to provably fair, imagine you were an evil bastard absolutely intent on stealing peoples money. Think about how you could steal their money without them noticing (e.g. using house bots that see how much they deposited and then beating them). Now, if you could come up with a way to steal peoples money undetectably, then the game is not provably fair. If you can steal money, but they will be able to see that you stole their money, then the game is provably fair. |
|
|
|
I must be wrong about the complexity of the encryption then, feel free to check out the certificate on the website
...or maybe you should Just go to your website with chrome, click on the lock next to https and go "details" to see the cert. Hint: it's RSA 2048 bits (e 65537). Nessus scan picked up nothing over "info" priority.
Um ok? So that just shows they don't check for CVE-2016-2107 vulnerability, that doesn't make it secure. See: https://dl.dropboxusercontent.com/spa/rmczv2tqcr196vz/gahrpmvr.pngIf i'm right about it, maybe you should, you know, edit your advertisements to avoid making those claims (about being identified and accountable) >< Normally I'd assume someone making fake claims like that is malicious, but I think in your case you genuinely don't know how this stuff works :/ Also on a side not (from reading that reddit thread) it seems you misunderstand provably fair. Being open-source and provably fair are orthogonal. Even if we can review or assume the open-sourced code is completely fair, we have no way of knowing that you are running that exact version on your server. |
|
|
|
A word on security:
All of our sites traffic is processed using HTTPS 128-bit encryption for maximum privacy and security.
Also this shows that we have registered with a trustworthy certificate authority and can be identified/held accountable for any fraudulent activity were it to occur on our site.
Huh? First of all, there's no way your key is 128 bits, no browser is going to accept a key that weak. Secondly your server is vulnerable to the recent padding oracle attack ( https://www.openssl.org/news/secadv/20160503.txt ) which almost invalidates the point of using https And lastly, "and can be identified/held accountable" is blatant misinformation. Your certificate (DV SSL) shows one thing, and one thing only: that it was issued to someone who controls the domain. I'm going to guess you already know this based on the fact you never had to prove who you were. And " for any fraudulent activity" is a empty claim, as you because as you know any cheating is 100% undetectable, as your game make no effort to be provably fair, and players have to 100% trust you that they lost =) |
|
|
|
Damn, this is dangerous. Don't be fooled by their social engineering shits. Those damn bot and script kiddies are really false!
the dangerous thing is, the bot supposedly works and is reasonably good (From what I've heard). But that doesn't make it guarantee it's safe or virus free  |
|
|
|
IF ANYONE IS USING THE POPULAR BUSTABREAKER BOT, PLEASE IMMEDIATELY CHANGE YOUR PASSWORDhttps://www.bustabit.com/update-passwordand make sure the email address is either not set, or set to an email you exclusively control. And then assume your computer likely has malware. I ran the bot from the site ( mmmbits . com) through totalvirus, and it came clean -- but I have very strong circumstantial evidence that would suggest the bot has a backdoor in it, that at the very least keylogs. I don't wish to accuse the bot author of anything without hard proof, but the facts are: * There have been multiple people reporting getting hacked, that have all used the bustabreaker executable. * Based on browser fingerprinting the person who did the hacking also was logged into @netstat a known alt of @gill_gates the creator of bustabreaker. * There is a ip address used in common between the hacker and gill_gates This leads me to the believe either that gill_gates is also a victim of the hacking or that gill_gates program is backdoored. I would strongly advice everyone who used this bot to assume the worst. (Note: this is because the bot is an executable, javascript bots that you run in the script editor don't pose the same level of risk of malware)
|
|
|
|
|
Show Posts
