Find a way to make the gambling provably fair for your users. Without this it will get difficult, no matter if you as the operator are anonymous or not. IF the site operates provably fair there is no need for you to be public. Math is always better than a pseudo-public identity which could still be a carefully laid out fake.
|
|
|
gweedo, you're hilarious. You blaming others of skewing the poll because it does not fit your expectation... This is pure awesomeness I just hope that also the devs have the serenity to not take your troll attempts too serious. And respect to everyone who tried to give you a polite and technically sound answer.
|
|
|
I just restarted the payment engine as it was offline for about 4 hours. All payments due within this timeframe were in state "Pending", but are now paid. Sorry for the trouble
|
|
|
We have setup btcd at our colocation facility and are using it to generate output similar to blockexplorer.com, have a look at blocksafari.com to see btcd-generated output. OMG. Thought my display is broken untill I realized that you have an amazing background there :-) Ontopic: Very interesting! Do you plan the rpc-interface to be a possbile drop-in replacement for bitcoind?
|
|
|
Update:You can now opt to hide your stats and sessions from public. If you don't want the world to see how much you are betting you can go to your account settings and click on "Anonymize me in public stats". Enabling this will anonymize or hide most of your personal information: - Your dashboard will not be available for other users
- Your player name, sessions and transactionIDs will be replaced by '****' in all public statistics
- Your personal statistics will not be available for other users
If you are logged in you will of course see all this information like usual. Note that this is only relevant for history and statistics. Your bets will still show up in the live bet log on the main screen, but users will not be able to open your dashboard or session details from there.
|
|
|
You could reduce the risk of double-spend attempts by actively distributing/resending the received transaction to as many nodes as possible. This makes it hard for the attacker to have success with a double-spend transaction as most clients should already know the first tx. But this will not help on all attack vectors.
|
|
|
Will you add 2-factor authentication?
Hi, You can activate OTP authentication here: Account securityWhoops, did not see this. Thanks!
|
|
|
Will you add 2-factor authentication?
|
|
|
Regarding the rounding issues: Rounding in the UI usually makes sense, so keep it there. But you could just add a tooltip to any rounded number containing the full-precision amount. This is the way I do it on my site and so far no one complained
|
|
|
Site will be down for a few minutes for system upgrade...
Up and running again! This upgrade *should* give a great performance boost on the load times. Let's see :-)
|
|
|
Site will be down for a few minutes for system upgrade...
|
|
|
I've played here, since SatoshiDice has been very slow lately. Seems to work well, but would like to see the number i rolled without having to click on every bet if possible.
Just rolled out a layout update: - The lucky number is now shown in your dashboard next to each bet
- Some more minor tweaks and fixes
|
|
|
All morality questions aside this is a clear warning:
If you use a hybrid/browser wallet you have a high risk of being compromised.
Although this has been discussed before multiple times i think this is the first time it actually happened. If the operator can do this kind of change the hacker of the site can do exactly the same.
|
|
|
I think some bot/script is trying to rip you / us off. I am getting a gazillion requests per second on bitbattle.me index page, without anyone clicking anything else. All are referring from " http://ad.a-ads.com/504". Requests come from different IPs, so probably a botnet producing clicks. This is really annoying, the site was basically DDos'd by these requests. Now I am rejecting all requests with that referrer... Is there any chance to stop that campaign? I have a feeling that most of my ad budget will be taken by that script kiddie...
|
|
|
Hi, today I finally made the transition to the new machine. The frontend is remaining on the old system, while bitcoind and backend is on the new system. All went smooth without noticable downtime. From the logs all seems fine, but please let me know if you experience any troubles. No need to change anything on user-side - IP and hostname for website and API access stay the same. I am quite confident that this will finally fix the downtimes experienced in the last weeks
|
|
|
I am totally blown away Awesome!
|
|
|
I've played here, since SatoshiDice has been very slow lately. Seems to work well, but would like to see the number i rolled without having to click on every bet if possible.
Good point. I'll add the lucky number to the dashboard
|
|
|
Rolled out another update tonight, which hopefully finally fixes the occasional double payment issue. (You just have to love multithread-multiprocess-multisite synchronization - So many things you can do wrong... )
|
|
|
The server is quite loaded at the moment. Not sure yet if this is some DDOS attack or just increased traffic, maybe due to SDice problems...
Looks like someone is trying to rip off Anonymous ads by automatically clicking on Ads, resulting in huge traffic. Traffic volume is now almost back to normal again.
|
|
|
The server is quite loaded at the moment. Not sure yet if this is some DDOS attack or just increased traffic, maybe due to SDice problems...
|
|
|
|