I wonder if there really is a system that works since these numbers are only pseudo-random?  Maybe the server sheet should automatically change every X rolls

yes, it may be more difficult to "know" your hash if the hash is refreshed every x rolls, it doesn't make it "more random".

random or pseudo-random is not important, what's important is the roll/seed/hash is "extremely difficult to predict" and "provably fair".

The system is fine as it is. As an investor (most of the time anyway), I'm more than happy with people thinking they have a system or a 'feel of the character' of their hash.

Also, while the 'lo' roll has a higher chance of winning than 'hi', the probability that this effect comes into play is 4.4 * 10^-34, which means it's a lot less likely than winning every lottery on the planet in the coming year and getting struck by lightning a few times along the way.

It's a perfectly viable business model, just not something with guaranteed short-term results. The site has had a single gambler bettings very large amounts and having above average luck, which took the house profit on some big swings. The house was up more than the theoretical 1% before, went down to something like -0.5% and has since then recovered to the current .26%. These results are still well within you can statistically expect.


4 days and 6 hours ago, dooglus made a database dump for people to run stats on. We can use that to make an estimate. At that point, 556K BTC had been wagered. Right now it's 624K. That translates to 16,000 BTC wagered per day, which is a little less than half of the invested amount. So with these numbers, you expect a little less than 0.5% daily increase on your investment. But these stats are extremely sensitive to variation.

Can't they just add in waits?

Thanks Rannasha for taking all these questions while I was sleeping.  I love how investors feel - uh - invested - and so take responsibility for helping out newcomers.  It's this feeling of community that I was hoping for when I made the site the way I did, with on-site chat and shared bankroll.

As for amounts wagered and invested, I occasionally update https://just-dice.com/wagered.txt with the amount wagered each day (UTC), and http://blockchain.info/charts/balance?address=14o7zMMUJkG6De24r3JkJ6USgChq7iWF86 pretty closely tracks the amount invested over time (it's the cold wallet balance, which doesn't include the amount I keep online to process day to day withdrawals, and does include player balances, which pretty much cancel each other out).

wagered.txt was just updated, btw.


It's not the throttling that broke the bots, it's the message that says "your bet is being delayed because you only bet X BTC".  Previously, when a message was received, it always came when the bet was finished, and so bots were coded to send their next bet whenever they saw a message.  This "your bet is delayed" message necessarily has to come before the bet has finished, so people can understand why the site seems slow.

If the bots wait for a 'result' message, they'll be fine.  Or if they just ignore the 'jdmsg' messages, that'll work too.

What are you doing to make the browser unresponsive?  Use setTimeout() to wait without burning CPU.

Nevar

Good luck with that lol

Haha yea I know.  I figure cause that's what I've lost on JD