heh? Considering you're up almost $40 and never had a delayed withdrawal or deposit, I must be a pretty bad scammer




...although that's pretty anecdotal. So I'd invite you to read the details our of provably fair: https://bitcointalk.org/index.php?topic=922898.0

If anyone wants to offer a 50% house edge, and users want to play a game where they're basically handing the casino money, I don't have a problem with it. But considering how highly unusual this is, I think they should take steps to make this extremely clear and explicit.

Showing the winning chance is good, but many people aren't fully aware of how this translates to house edge

Thanks for letting me know. I've posted on the thread, and temporary disabled API access for their app until they take some steps to be less misleading.

Thanks, based on this, I've credited to peoples accounts:

1. Dexon: 0.1
2. Venusian:  0.05 BTC
3. BertBot: 0.04 BTC
4. Snailman: 0.03 BTC
5. ?
6. Fish: 0.02
7. ndnhc: 0.02
8. ?

Quick note to bustabit players: Absolutely no ownership changes will happen ever without considerable notice. Bustabit also typically makes the sum of players balances by operating legitimately in a two week period. And by being provably fair any cheating is detectable and would destroy the site; so the chance of someone interested in buying the site to scam is virtually nil.


As many of you know, bustabit is one of the most popular bitcoin casinos. In total we've had over 137k bitcoin wagered, and over the last 3 months an average of 501 btc wager a day, with reasonably significant growth (e.g. the last month had 668 BTC wagered a day).

We're typically one of the top casinos: https://thebitcoinstrip.com/leaderboard.html
and you can see our historical stats: https://thebitcoinstrip.com/bustabit-stats.html
and the latest snapshot: https://www.bustabit.com/stats

Our historical house edge has averaged 0.35% of the amount wagered, so as you can see it's running quite profitably. (I spend around $250/month on hosting, and about 0.5 BTC/month on promotions and giveways).


While I am by no means in a rush to sell, I'd be very open to the opportunity of freeing up some of my time for MoneyPot (my other venture, which has taken priority as of late). And due the non-atomic bet nature of bustabit it is not a good candidate for MoneyPot integration, and has been run 100% independently.


Some things to know:
  * The source code is available (bustabit-*) under the terms of the AGPLv3, which means anyone can make a clone provided they keep all modifications under the same license. However we retain total copyright, which gives us the ability to relicense the code if wanted (just not retroactively for old versions people downloaded under the AGPL)

 * We regularly turn down whales who want to bet more than 1 BTC, so this is a huge opportunity to grow

 * The site itself runs fine a bankroll of ~300 BTC, although that puts it at a >1x kelly risk

 * The site is written completely in node.js and postgres


 I'm looking for something that would be a silky smooth transition, and for that I'd prefer to conclude any business in person with a technical person where I can walk over all aspects of the site and transition everything (e.g. generate a new provably fair chain, that I don't have access to)


< closing due to lack of interest >

As people mentioned, check the deposit address in: https://www.moneypot.com/me/receive

and it lists how much money has been received there (confirmed and unconfirmed) and also if it is associated with a particular app or not.

If there's an issue please use the support link at the top of every page.

Using that support leads to much faster responses (the large majority of issues get a handled within an hour, as I get notifications on support issues, but only check the forums when procrastinating), and if you are logged in, it authenticates you and contains your account information which allows me to look into it for you and communicate with you in a direct/private matter.

 

Was just private messaged with a solution! Thanks very much! I will implement this today

The same force that makes people not stop at winning 5 BTC, makes them not stop when they're 10, or 20 or even 40 btc. It's pretty easy in hindsight for people to be like: "Why didn't they just cashout at <all time high>" but the reality is they wouldn't have reached that all time high if they had a cashout attitude.

However, every so often I do see players who playing with: "I'm going to either lose all my money, or win X btc" and most of the time, they do lose, but those that do win end up cashing out at their high.

Yeah, I'm looking into how to solve this, but don't see any great solution. The problem is when recaptcha uses one of those copy&paste text recaptchas it doesn't seem to trigger the submit event. It almost seems like a recaptcha bug.

One possible solution is to have a more elaborate login process, that doesn't always require a recaptcha (e.g. enter username first, and then only suspitious ip addresses or user accounts will be presented with a recaptcha). For people who are very confident about their password security, they could disable recaptchas for their account completely

You can check the apps commissions here https://www.moneypot.com/full-stats.json (all values are in satoshis) for anyone interested. Please note this doesn't include expenses (e.g. advertising, rakebacks, promotions etc)

Why not just use the MP faucet on your own site? We foot the bill, not you =)

(And the faucet cool-down is global, so you can't abuse it by rotating through MP sites)

There's probably some clever solutions, but you can do it pretty easily by first implementing the JD solution and (on demand) generating a new salt for each in bet in the sequence. Before each bet, you tell the client what the `sha256(outcome + '|' + salt)` is going to be, and after after each game you can reveal both the outcome (before applying the client seed) and the salt.  The benefit of that, would be you would have two independent ways to verify bets, either in batch (great for humans) or realtime (great for bots).  However, I'm highly skeptical that the overhead and complexity is worth while for the 0.01% of people who care (and who already have no problems verifying their bets).

You need to first go to the site, and then add it for it to show up in your apps tab. Only a select few games are "featured" which show-up regardless of being added or not

Just to be clear, you can self-verify MP bets too. It's just a pain in the ass.

Here's the procedure for manual verification both:

Just-Dice:
1. Record the server seed hash
2. Change the client seed to something you picked
3. <make 1 or more bets> (and remember the order, direction and amount you bet)
4. Ask the server to reveal the server seed
5. Use a script to generate the outcomes
6. Compare the lists

MoneyPot:
1. Record the server seed hash
2. Change the client seed to something you picked
3. <make 1 bet>
4. Use a script to check the outcome, given the bet result (and client seed)
5. Compare


--

So the advantage to JD's scheme, is if you trust your memory (or bet predictably) you can bet over and over. It's honestly much better for a human. But MPs advantage is it happens on a per-bet basis, and if you trust the verification script you can automate it. All MP casinos (with the exception of DustDice) are third-party, and their interests strongly align with players  (they make more money by having players win than lose)

They're just different. If you're a human verifying the bets, Just-Dice's is strictly better. If you're automatically verifying bets, MoneyPot's is better as it's simpler, and you can do it immediately.  Automatically verifying bets however, has the downside that the user needs to trust the auto-verification.

Actually the earlier prototypes of MoneyPot used to use Just-Dice's provably fair scheme, but it was too difficult for apps to verify (they need to keep their own independent, and complete record, and batch verify them) especially in the case of things like races (apps parallelizing bets for instance) and non-exclusive api calls (e.g. even as simple as two tabs open).

Actually, for instance one thing I want to build is a browser-plugin that MITM all bets to moneypot  (regardless of the casino it originates from) and randomizes the client-seed and verifies the bet (and gives a warning to the user if it doesn't). Such tools like this wouldn't really be feasible with JDs scheme.

But however, if you expect end-users to verify the bets, I'd definitely use JD's scheme.

--

Edit: It's actually quite possible to combine both schemes, in one that allows both batch verification AND realtime verification. Something I considered doing, but laziness won the day, and I'm a sucker for simplicity.

Just as a reminder, during the downtime you have total access to your money: https://www.moneypot.com/apps/14-betterbets  and are able to continue to deposit and withdraw, so nothing to worry about =)

Probably the primary advantage for is that it lends MoneyPot more legitimacy, and establishes a paper-trail to both the entity and me personally. And probably the primary disadvantage is that the limited-liability aspect of a company (i.e. the company can independently go bankrupt to me).

But really, it's just an expensive piece of paper that points back to me, which I hope gives people some confidence that I'm not just a cheap pop-up scam.

I'm a bit of a bitcoin purist at heart, so unless something hugely changed in the landscape I don't have any plans to add altcoins now or the future. e.g. While I don't think it will, and hope it won't, but for pragmatic reasons might be forced to add a "BitcoinXT/BitcoinCore" currencies if bitcoin continuously forked and both held value

That's actually why we created this "event". We proved we did it before the block was mined, exactly to disprove this:


if you don't trust the dates on this forum (which you might not, because I can edit the OP) you can check the critical details in a variety of ways, that all happened before that block was mined:
a) The fact people quoted me link
b) It was on reddit link
c) It was emailed to dooglus (you can ask him, and he can find it and get the date)
d) It's archived on archive.org  (link)

and if that's not enough, I actually timestamped it on the blockchain (before block 339300) which should be complete proof. I don't have the link on me right now, but can dig through my email and find it if you like.






it is =)


You could make a script that finds a "bad" server seed, but it's unlikely to be that bad. The probability of a server seed having no games > 2.0x is like 0.50990099^10e6 (making some generous assumptions about sha256), which is just gazillions of times harder than just finding bitcoin private keys, or my server seed

Yeah, you can get/verify the details at the national registry of costa rica ( rnpdigital.com ). The basic records are free and you can check online.

After you create an account and log in, you go to: "Consultas Gratuitas" and then under "Personas Juridicas" look for "Consulta por Nombre Social" and type in "MoneyPot" and you'll see us there =)