Running ANYTHING java based, having to use Java based junk in the enterprise, I can tell you I have never once seen a java based program that was worth anything in high availability/heavy load environments. Couple that with the fact that without some severe tweaks, the memory limits of the java VM leave a LOT to be desired. I'll stick with native code, thanks. That said, it's usually the interface that is complete FAIL with java crap
...
But there are so many other problems with java scalability wise that it's just too unstable and problematic to build a business off of Of course I'm not using poolserverj, and I like native code too, but you are a bit wrong in this part :) |
|
|
|
|
One of blocks was (possibly) marked as invalid instead of another today, I'm checking this now.
Stats data for this block may be shown incorrectly until this issue is resolved.
UPDATE:
Looks like I found what's happened.
Also, two blocks at 24.09 16:37:01 GMT are shown in the wrong order.
|
|
|
|
|
UPDATE:
E-mail notifications are enabled for everyone.
How does it works:
This feature doesn't depends on submitted shares because they are random and inconsistent. Instead, getwork requests are monitored.
Failure condition is triggered when no getwork requests are received from the worker for at least 5 minutes. Notification is issued in 0 to 6 minutes
after this, so you should receive a message in 5 to 11 (worst case) minutes since the failure.
You can enable or disable this notification for each worker separately at it's settings page. Only users with confirmed e-mail can use this feature.
|
|
|
|
On the stats page in the line that contains
"Average shares per block: 1672968"
What is the time frame for this average? Is it for the just the last block, which wouldn't be an average, or is it the average for this difficulty? Since the last difficulty adjustment. |
|
|
|
Average shares per block: 1670916 (-5.1%)
Average in last 24 hours: 2011670 (+12.7%) Hmm, looks like I'm dividing it in the wrong order. Fixed. Thanks for your report. You forgot to mention that you REVERSED the meaning of positive and negative. That may confuse some :) Oh... I'll fix it back again :) |
|
|
|
Still searching................ It's not on the site. Don't worry, it will be enabled for everyone very soon, just after I'll see that it sends notifications to some of testers. |
|
|
|
|
Attention to beta-testers:
You can test e-mail notifications (enabled at worker configuration pages if your e-mail is confirmed).
Notifications are sent if your worker stopped requesting new work for more than 5 minutes.
E-mail can be sent after up to 13 minutes since worker failure.
|
|
|
|
How does one become a beta tester? Anyone can become a beta tester if he finds out how to do it. |
|
|
|
|
Attention to beta-testers:
You can enable e-mail notifications in some worker's control page if your e-mail is confirmed.
This failure detection is not based on received shares and it's not affected by user-adjustable threshold.
It won't be triggered by any problems lasted less than 5 minutes.
Please report via PM if you don't receive e-mail notification after your worker failed/disconnected for more than 13 minutes.
|
|
|
|
The block who generated the most BTC ever is block 139,896: it generated 66.20996865 BTC! Actually only 50 BTC were generated, the fee is taken from already existing coins. |
|
|
|
Average shares per block: 1670916 (-5.1%)
Average in last 24 hours: 2011670 (+12.7%) Hmm, looks like I'm dividing it in the wrong order. Fixed. Thanks for your report. |
|
|
|
|
Nice idea :)
Don't forget to take videos.
|
|
|
|
|
Sending wallet.dat may be good enough only if you know for sure that the recipient doesn't have his own wallet yet. Otherwise it would be more difficult to reclaim those coins.
|
|
|
|
|
I would recommend adding at least the sum to the possible "standart" bitcoin QR code. And better is to include both the sum and a field for comments (like item name).
I think that including the sum is very important.
With those fields a customer just has to point his smartphone at the bill / price tag / invoice, check the value and press the "Pay" button.
|
|
|
|
|
Deepbit's luckmeter (user hashrate estimation) is updated once per minute and calculated over a user-adjustable window, so it's even more live than the most live statistics of any mining pool (jk) :)
But this is not affected by finding blocks and no special recalculations occur at that moment, so that's not the reason.
|
|
|
|
But under that paradigm, pools, as long as they don't mod their software to increase the number of outgoing connections, are limited to 8 connections... Hm... I don't think that any serious pool runs stock bitcoind anyway :) |
|
|
|
|
Counting shares for more than 24h is a good measure.
Also you may compare actual payouts, but this would require more than a couple of days to average out bad/good luck.
|
|
|
|
do you have any plans for merged mining? No plans for merged mining at this moment. |
|
|
|
Still not able to login, all i did before this was boot into windows to play some games which ive done 3-4 times before this with no problems starting up the miner again..... Do you know that main account password and worker's password are not always the same ? If you change your site password, it doesn't affects other passwords. Try changing your worker password to something simple and launch the miner again. Address for mining is pit.deepbit.net:8332 |
|
|
|
|
Show Posts
