Why is the site down? Are we getting DDOS'ed again?
Something is causing the website to sometimes respond slowly, which can cause Cloudflare to think it is down. I'll need to investigate that..
Topic: Bitminter client (Windows/Linux/Mac) - page 28. (Read 655007 times)
Something is causing the website to sometimes respond slowly, which can cause Cloudflare to think it is down. I'll need to investigate that..
Why is the site down? Are we getting DDOS'ed again?
The hashrate meter is working for me now. Don't know if it is because you changed anything. I didn't change anything.
No, nothing changed here. It may be a bug that happens rarely.
It happens sometimes, not every time. I haven't kept a log so I can't tell you how often it happens. But more than just rarely. Maybe 1 in 4 times.
Hope you can find what causes it. Although it's not that important a function, it is a nice feature.
The hashrate meter is working for me now. Don't know if it is because you changed anything. I didn't change anything.
No, nothing changed here. It may be a bug that happens rarely.
Yes the accepted proof of work still goes up.
Here is a copy of the log:
[...]
Here is a copy of the log:
[...]
Hmm, looks like everything is working, except for the hashrate display. Very odd. I've never seen that happen myself. Maybe it only happens with Icarus/ASICminer devices. How often does it get stuck at zero that way? Might be a difficult bug to catch.
The hashrate meter is working for me now. Don't know if it is because you changed anything. I didn't change anything.
Yes the accepted proof of work still goes up.
Here is a copy of the log:
[...]
Here is a copy of the log:
[...]
Hmm, looks like everything is working, except for the hashrate display. Very odd. I've never seen that happen myself. Maybe it only happens with Icarus/ASICminer devices. How often does it get stuck at zero that way? Might be a difficult bug to catch.
Thanks for the response. Just looking for a bit more education.
My understanding is that it is mostly luck that determines whether we build a new block.
My understanding is that it is mostly luck that determines whether we build a new block.
The more hashrate the better the chance to get blocks. With a high hashrate pool you get several blocks per day, which means several small payments to you as a miner. Mining solo or in a tiny pool it might take months or even years of nothing before you got a big payment. Most miners prefer the low variance with frequent small payments.
Why does the Bitminter client acceleratometer still show 0.00 after 7 days of mining?
I do get the coins added to my account.
I do get the coins added to my account.
Must be a bug. I see your Icarus/block erupter shows a hashrate, but the total hashrate is still zero. I haven't seen this happening myself, so I'm not sure what would cause it.
This problem is still recurring with me. I hope you can fix it.
Are there any log messages when this happens? That's the text area at the bottom.
Do accepted proofs of work still go up (the yellow boxes)? Or is everything just stuck, like the erupter hashrate staying at the exact same number instead of going slightly up and down like usual?
Yes the accepted proof of work still goes up.
Here is a copy of the log:
2013.08.10 [17:21] BitMinter Client v1.4.0 started
2013.08.10 [17:21] Hint: Use performance mode for best GPU results (bottom right button)
2013.08.10 [17:21] No OpenCL-compatible GPUs detected
2013.08.10 [17:21] Lacking OpenCL support. If you want to use GPUs, please install the latest drivers from your graphics card manufacturer.
2013.08.10 [17:21] Probing all ports for external devices
2013.08.10 [17:21] FPGA device detected on COM4: Icarus
2013.08.10 [17:21] Device [Icarus (COM4)] started
2013.08.10 [17:21] New connection established.
2013.08.10 [17:21] Block change detected due to new work ID
2013.08.10 [17:21] Difficulty is now 37392766
2013.08.10 [17:21] Server now building on top of a new block - ditching stale work
2013.08.10 [17:21] Icarus (COM4): Tuning timers.
2013.08.10 [17:21] New connection established.
2013.08.10 [17:21] Icarus (COM4): Command response 15 ms, hash rate 336.1 Mhps.
2013.08.10 [17:22] New connection established.
2013.08.10 [17:23] Connection timed out
2013.08.10 [17:23] Connection closed after 4 request-response exchanges.
2013.08.10 [17:24] New connection established.
2013.08.10 [17:25] Block change detected due to long poll response
2013.08.10 [17:25] Long poll connection received block change notification
2013.08.10 [17:25] Server now building on top of a new block - ditching stale work
2013.08.10 [17:25] Connection closed after 24 request-response exchanges.
2013.08.10 [17:27] New connection established.
2013.08.10 [17:27] Connection closed after 0 request-response exchanges.
2013.08.10 [17:28] Connection closed after 15 request-response exchanges.
2013.08.10 [17:28] New connection established.
2013.08.10 [17:30] Connection closed after 2 request-response exchanges.
2013.08.10 [17:30] New connection established.
2013.08.10 [17:31] Block change detected due to long poll response
2013.08.10 [17:31] Long poll connection received block change notification
2013.08.10 [17:31] Server now building on top of a new block - ditching stale work
2013.08.10 [17:31] Block change detected due to long poll response
2013.08.10 [17:31] Long poll connection received block change notification
2013.08.10 [17:31] Server now building on top of a new block - ditching stale work
2013.08.10 [17:31] Block change detected due to long poll response
2013.08.10 [17:31] Long poll connection received block change notification
2013.08.10 [17:31] Server now building on top of a new block - ditching stale work
2013.08.10 [17:32] New connection established.
2013.08.10 [17:33] Connection closed after 0 request-response exchanges.
2013.08.10 [17:33] Connection timed out
2013.08.10 [17:33] Connection closed after 15 request-response exchanges.
2013.08.10 [17:33] New connection established.
2013.08.10 [17:35] New connection established.
2013.08.10 [17:35] Connection timed out
2013.08.10 [17:35] Connection closed after 10 request-response exchanges.
2013.08.10 [17:36] Block change detected due to long poll response
2013.08.10 [17:36] Long poll connection received block change notification
2013.08.10 [17:36] Server now building on top of a new block - ditching stale work
2013.08.10 [17:37] New connection established.
2013.08.10 [17:38] Connection closed after 0 request-response exchanges.
2013.08.10 [17:39] New connection established.
2013.08.10 [17:39] Block change detected due to long poll response
2013.08.10 [17:39] Long poll connection received block change notification
2013.08.10 [17:39] Server now building on top of a new block - ditching stale work
2013.08.10 [17:39] Connection closed after 0 request-response exchanges.
2013.08.10 [17:40] New connection established.
2013.08.10 [17:41] Connection closed after 35 request-response exchanges.
2013.08.10 [17:42] New connection established.
2013.08.10 [17:43] Connection closed after 9 request-response exchanges.
2013.08.10 [17:43] New connection established.
2013.08.10 [17:44] Block change detected due to long poll response
2013.08.10 [17:44] Long poll connection received block change notification
2013.08.10 [17:44] Server now building on top of a new block - ditching stale work
2013.08.10 [17:44] Connection closed after 0 request-response exchanges.
2013.08.10 [17:45] New connection established.
2013.08.10 [17:46] Connection closed after 16 request-response exchanges.
2013.08.10 [17:46] New connection established.
2013.08.10 [17:47] Connection closed after 0 request-response exchanges.
2013.08.10 [17:47] New connection established.
2013.08.10 [17:48] Block change detected due to long poll response
2013.08.10 [17:48] Long poll connection received block change notification
2013.08.10 [17:48] Server now building on top of a new block - ditching stale work
2013.08.10 [17:48] Communication error: Connection closed
2013.08.10 [17:48] Connection closed after 0 request-response exchanges.
2013.08.10 [17:48] Block change detected due to long poll response
2013.08.10 [17:48] Long poll connection received block change notification
2013.08.10 [17:48] Server now building on top of a new block - ditching stale work
2013.08.10 [17:51] Connection closed after 31 request-response exchanges.
2013.08.10 [17:51] New connection established.
2013.08.10 [17:53] Block change detected due to long poll response
2013.08.10 [17:53] Long poll connection received block change notification
2013.08.10 [17:53] Server now building on top of a new block - ditching stale work
2013.08.10 [17:53] New connection established.
2013.08.10 [17:55] Connection closed after 4 request-response exchanges.
2013.08.10 [17:55] New connection established.
2013.08.10 [17:56] Block change detected due to long poll response
2013.08.10 [17:56] Long poll connection received block change notification
2013.08.10 [17:56] Server now building on top of a new block - ditching stale work
2013.08.10 [17:56] Block change detected due to long poll response
2013.08.10 [17:56] Long poll connection received block change notification
2013.08.10 [17:56] Server now building on top of a new block - ditching stale work
2013.08.10 [17:56] Block change detected due to new work ID
2013.08.10 [17:56] Server now building on top of a new block - ditching stale work
2013.08.10 [17:56] Block change detected due to new work ID
2013.08.10 [17:56] Server now building on top of a new block - ditching stale work
2013.08.10 [17:56] Connection closed after 0 request-response exchanges.
2013.08.10 [17:59] Connection closed after 45 request-response exchanges.
2013.08.10 [17:59] New connection established.
2013.08.10 [18:01] Connection closed after 21 request-response exchanges.
2013.08.10 [18:01] New connection established.
2013.08.10 [18:02] New connection established.
2013.08.10 [18:03] Connection closed after 11 request-response exchanges.
2013.08.10 [18:04] Block change detected due to long poll response
2013.08.10 [18:04] Long poll connection received block change notification
2013.08.10 [18:04] Server now building on top of a new block - ditching stale work
2013.08.10 [18:05] Block change detected due to long poll response
2013.08.10 [18:05] Long poll connection received block change notification
2013.08.10 [18:05] Server now building on top of a new block - ditching stale work
2013.08.10 [18:06] New connection established.
2013.08.10 [18:07] Connection closed after 0 request-response exchanges.
2013.08.10 [18:09] New connection established.
2013.08.10 [18:10] Connection closed after 0 request-response exchanges.
2013.08.10 [18:10] Connection closed after 13 request-response exchanges.
2013.08.10 [18:11] New connection established.
2013.08.10 [18:11] Block change detected due to long poll response
2013.08.10 [18:11] Long poll connection received block change notification
2013.08.10 [18:11] Server now building on top of a new block - ditching stale work
2013.08.10 [18:12] New connection established.
2013.08.10 [18:13] Connection closed after 0 request-response exchanges.
2013.08.10 [18:13] Connection closed after 15 request-response exchanges.
2013.08.10 [18:14] New connection established.
2013.08.10 [18:14] New connection established.
2013.08.10 [18:15] Connection timed out
2013.08.10 [18:15] Connection closed after 3 request-response exchanges.
2013.08.10 [18:15] New connection established.
2013.08.10 [18:16] Connection closed after 0 request-response exchanges.
2013.08.10 [18:16] Connection closed after 47 request-response exchanges.
2013.08.10 [18:16] Block change detected due to long poll response
2013.08.10 [18:16] Long poll connection received block change notification
2013.08.10 [18:16] Server now building on top of a new block - ditching stale work
2013.08.10 [18:16] New connection established.
2013.08.10 [18:16] Block change detected due to long poll response
2013.08.10 [18:16] Long poll connection received block change notification
2013.08.10 [18:16] Server now building on top of a new block - ditching stale work
2013.08.10 [18:16] Work rejected. Server says: Stale proof of work
2013.08.10 [18:17] Block change detected due to long poll response
2013.08.10 [18:17] Long poll connection received block change notification
2013.08.10 [18:17] Server now building on top of a new block - ditching stale work
2013.08.10 [18:18] New connection established.
2013.08.10 [18:18] Connection timed out
2013.08.10 [18:18] Connection closed after 12 request-response exchanges.
2013.08.10 [18:18] New connection established.
2013.08.10 [18:19] Connection closed after 0 request-response exchanges.
2013.08.10 [18:20] Connection closed after 12 request-response exchanges.
2013.08.10 [18:20] New connection established.
2013.08.10 [18:21] Block change detected due to long poll response
2013.08.10 [18:21] Long poll connection received block change notification
2013.08.10 [18:21] Server now building on top of a new block - ditching stale work
2013.08.10 [18:22] New connection established.
2013.08.10 [18:23] Block change detected due to long poll response
2013.08.10 [18:23] Long poll connection received block change notification
2013.08.10 [18:23] Server now building on top of a new block - ditching stale work
2013.08.10 [18:23] Connection closed after 13 request-response exchanges.
2013.08.10 [18:24] Connection closed after 9 request-response exchanges.
2013.08.10 [18:25] New connection established.
2013.08.10 [18:26] Block change detected due to long poll response
2013.08.10 [18:26] Long poll connection received block change notification
2013.08.10 [18:26] Server now building on top of a new block - ditching stale work
2013.08.10 [18:26] Block change detected due to long poll response
2013.08.10 [18:26] Long poll connection received block change notification
2013.08.10 [18:26] Server now building on top of a new block - ditching stale work
2013.08.10 [18:28] New connection established.
2013.08.10 [18:28] Block change detected due to long poll response
2013.08.10 [18:28] Long poll connection received block change notification
2013.08.10 [18:28] Server now building on top of a new block - ditching stale work
2013.08.10 [18:28] Block change detected due to long poll response
2013.08.10 [18:28] Long poll connection received block change notification
2013.08.10 [18:28] Server now building on top of a new block - ditching stale work
2013.08.10 [18:28] Connection closed after 0 request-response exchanges.
2013.08.10 [18:29] New connection established.
2013.08.10 [18:30] Connection closed after 0 request-response exchanges.
2013.08.10 [18:31] Connection closed after 33 request-response exchanges.
2013.08.10 [18:31] New connection established.
2013.08.10 [18:32] Connection closed after 3 request-response exchanges.
2013.08.10 [18:32] New connection established.
2013.08.10 [18:32] Work rejected. Server says: Stale proof of work
2013.08.10 [18:32] Block change detected due to new work ID
2013.08.10 [18:32] Server now building on top of a new block - ditching stale work
2013.08.10 [18:32] Block change detected due to long poll response
2013.08.10 [18:32] Long poll connection received block change notification
2013.08.10 [18:32] Server now building on top of a new block - ditching stale work
2013.08.10 [18:33] Block change detected due to long poll response
2013.08.10 [18:33] Long poll connection received block change notification
2013.08.10 [18:33] Server now building on top of a new block - ditching stale work
2013.08.10 [18:33] Connection closed after 10 request-response exchanges.
2013.08.10 [18:33] New connection established.
2013.08.10 [18:34] New connection established.
2013.08.10 [18:35] Connection closed after 0 request-response exchanges.
2013.08.10 [18:37] New connection established.
2013.08.10 [18:38] Connection closed after 19 request-response exchanges.
2013.08.10 [18:38] Block change detected due to long poll response
2013.08.10 [18:38] Long poll connection received block change notification
2013.08.10 [18:38] Server now building on top of a new block - ditching stale work
2013.08.10 [18:39] Block change detected due to long poll response
2013.08.10 [18:39] Long poll connection received block change notification
2013.08.10 [18:39] Server now building on top of a new block - ditching stale work
2013.08.10 [18:41] Connection closed after 16 request-response exchanges.
2013.08.10 [18:41] New connection established.
2013.08.10 [18:41] New connection established.
2013.08.10 [18:42] Connection closed after 0 request-response exchanges.
2013.08.10 [18:42] New connection established.
2013.08.10 [18:43] Connection closed after 0 request-response exchanges.
2013.08.10 [18:44] Connection closed after 29 request-response exchanges.
2013.08.10 [18:45] New connection established.
2013.08.10 [18:45] New connection established.
2013.08.10 [18:45] Block change detected due to long poll response
2013.08.10 [18:45] Long poll connection received block change notification
2013.08.10 [18:45] Server now building on top of a new block - ditching stale work
2013.08.10 [18:45] Connection closed after 0 request-response exchanges.
2013.08.10 [18:46] Block change detected due to long poll response
2013.08.10 [18:46] Long poll connection received block change notification
2013.08.10 [18:46] Server now building on top of a new block - ditching stale work
2013.08.10 [18:47] New connection established.
2013.08.10 [18:48] Connection timed out
2013.08.10 [18:48] Connection closed after 20 request-response exchanges.
2013.08.10 [18:51] Connection closed after 21 request-response exchanges.
2013.08.10 [18:51] New connection established.
2013.08.10 [18:51] New connection established.
2013.08.10 [18:52] Connection closed after 4 request-response exchanges.
2013.08.10 [18:54] New connection established.
2013.08.10 [18:54] Connection closed after 13 request-response exchanges.
2013.08.10 [18:54] Block change detected due to long poll response
2013.08.10 [18:54] Long poll connection received block change notification
2013.08.10 [18:54] Server now building on top of a new block - ditching stale work
2013.08.10 [18:55] Connection closed after 6 request-response exchanges.
2013.08.10 [18:55] New connection established.
2013.08.10 [18:57] Block change detected due to long poll response
2013.08.10 [18:57] Long poll connection received block change notification
2013.08.10 [18:57] Server now building on top of a new block - ditching stale work
2013.08.10 [18:58] Connection closed after 8 request-response exchanges.
2013.08.10 [18:58] New connection established.
2013.08.10 [18:59] Connection closed after 7 request-response exchanges.
2013.08.10 [19:00] New connection established.
2013.08.10 [19:00] New connection established.
2013.08.10 [19:01] Block change detected due to long poll response
2013.08.10 [19:01] Long poll connection received block change notification
2013.08.10 [19:01] Server now building on top of a new block - ditching stale work
2013.08.10 [19:01] Connection closed after 0 request-response exchanges.
2013.08.10 [19:03] New connection established.
2013.08.10 [19:03] Connection closed after 0 request-response exchanges.
2013.08.10 [19:04] New connection established.
2013.08.10 [19:04] Connection closed after 23 request-response exchanges.
2013.08.10 [19:06] Connection closed after 23 request-response exchanges.
2013.08.10 [19:06] New connection established.
2013.08.10 [19:07] Connection closed after 4 request-response exchanges.
2013.08.10 [19:07] New connection established.
2013.08.10 [19:08] Connection closed after 6 request-response exchanges.
2013.08.10 [19:08] New connection established.
2013.08.10 [19:09] New connection established.
2013.08.10 [19:10] Connection closed after 4 request-response exchanges.
2013.08.10 [19:10] Block change detected due to long poll response
2013.08.10 [19:10] Long poll connection received block change notification
2013.08.10 [19:10] Server now building on top of a new block - ditching stale work
2013.08.10 [19:10] New connection established.
2013.08.10 [19:10] Block change detected due to long poll response
2013.08.10 [19:10] Long poll connection received block change notification
2013.08.10 [19:10] Server now building on top of a new block - ditching stale work
2013.08.10 [19:10] Block change detected due to long poll response
2013.08.10 [19:10] Long poll connection received block change notification
2013.08.10 [19:10] Server now building on top of a new block - ditching stale work
2013.08.10 [19:10] Connection closed after 0 request-response exchanges.
2013.08.10 [19:12] Block change detected due to long poll response
2013.08.10 [19:12] Long poll connection received block change notification
2013.08.10 [19:12] Server now building on top of a new block - ditching stale work
2013.08.10 [19:12] Block change detected due to long poll response
2013.08.10 [19:12] Long poll connection received block change notification
2013.08.10 [19:12] Server now building on top of a new block - ditching stale work
2013.08.10 [19:12] Block change detected due to long poll response
2013.08.10 [19:12] Long poll connection received block change notification
2013.08.10 [19:12] Server now building on top of a new block - ditching stale work
2013.08.10 [19:13] Connection closed after 21 request-response exchanges.
2013.08.10 [19:13] New connection established.
2013.08.10 [19:14] New connection established.
2013.08.10 [19:14] Connection closed after 7 request-response exchanges.
2013.08.10 [19:15] Connection closed after 9 request-response exchanges.
2013.08.10 [19:16] New connection established.
2013.08.10 [19:17] New connection established.
2013.08.10 [19:17] Connection closed after 20 request-response exchanges.
2013.08.10 [19:17] New connection established.
2013.08.10 [19:18] Connection timed out
2013.08.10 [19:18] Connection closed after 12 request-response exchanges.
2013.08.10 [19:19] New connection established.
2013.08.10 [19:20] Connection closed after 0 request-response exchanges.
2013.08.10 [19:20] Block change detected due to long poll response
2013.08.10 [19:20] Long poll connection received block change notification
2013.08.10 [19:20] Server now building on top of a new block - ditching stale work
2013.08.10 [19:20] Block change detected due to new work ID
2013.08.10 [19:20] Server now building on top of a new block - ditching stale work
2013.08.10 [19:20] Block change detected due to long poll response
2013.08.10 [19:20] Long poll connection received block change notification
2013.08.10 [19:20] Server now building on top of a new block - ditching stale work
2013.08.10 [19:21] Block change detected due to long poll response
2013.08.10 [19:21] Long poll connection received block change notification
2013.08.10 [19:21] Server now building on top of a new block - ditching stale work
2013.08.10 [19:21] Block change detected due to new work ID
2013.08.10 [19:21] Server now building on top of a new block - ditching stale work
2013.08.10 [19:21] Block change detected due to long poll response
2013.08.10 [19:21] Long poll connection received block change notification
2013.08.10 [19:21] Server now building on top of a new block - ditching stale work
2013.08.10 [19:23] Block change detected due to long poll response
2013.08.10 [19:23] Long poll connection received block change notification
2013.08.10 [19:23] Server now building on top of a new block - ditching stale work
2013.08.10 [19:24] Block change detected due to long poll response
2013.08.10 [19:24] Long poll connection received block change notification
2013.08.10 [19:24] Server now building on top of a new block - ditching stale work
2013.08.10 [19:26] Connection closed after 49 request-response exchanges.
2013.08.10 [19:26] Block change detected due to long poll response
2013.08.10 [19:26] Long poll connection received block change notification
2013.08.10 [19:26] Server now building on top of a new block - ditching stale work
2013.08.10 [19:26] New connection established.
2013.08.10 [19:27] New connection established.
2013.08.10 [19:28] Connection closed after 0 request-response exchanges.
2013.08.10 [19:28] Connection closed after 7 request-response exchanges.
2013.08.10 [19:28] New connection established.
2013.08.10 [19:29] Connection closed after 3 request-response exchanges.
2013.08.10 [19:29] New connection established.
2013.08.10 [19:30] Block change detected due to long poll response
2013.08.10 [19:30] Long poll connection received block change notification
2013.08.10 [19:30] Server now building on top of a new block - ditching stale work
2013.08.10 [19:31] Connection closed after 13 request-response exchanges.
2013.08.10 [19:31] New connection established.
2013.08.10 [19:34] Connection closed after 15 request-response exchanges.
2013.08.10 [19:34] New connection established.
2013.08.10 [19:34] New connection established.
2013.08.10 [19:35] Connection closed after 0 request-response exchanges.
2013.08.10 [19:35] Connection closed after 9 request-response exchanges.
2013.08.10 [19:35] New connection established.
2013.08.10 [19:36] New connection established.
2013.08.10 [19:37] Connection closed after 0 request-response exchanges.
2013.08.10 [19:37] New connection established.
2013.08.10 [19:38] Connection closed after 0 request-response exchanges.
2013.08.10 [19:40] Connection closed after 10 request-response exchanges.
2013.08.10 [19:40] New connection established.
2013.08.10 [19:40] Block change detected due to long poll response
2013.08.10 [19:40] Long poll connection received block change notification
2013.08.10 [19:40] Server now building on top of a new block - ditching stale work
2013.08.10 [19:41] Connection closed after 9 request-response exchanges.
2013.08.10 [19:41] Block change detected due to long poll response
2013.08.10 [19:41] Long poll connection received block change notification
2013.08.10 [19:41] Server now building on top of a new block - ditching stale work
2013.08.10 [19:41] New connection established.
2013.08.10 [19:43] New connection established.
2013.08.10 [19:44] Block change detected due to long poll response
2013.08.10 [19:44] Long poll connection received block change notification
2013.08.10 [19:44] Server now building on top of a new block - ditching stale work
2013.08.10 [19:44] Connection closed after 2 request-response exchanges.
2013.08.10 [19:45] Connection closed after 14 request-response exchanges.
2013.08.10 [19:45] New connection established.
2013.08.10 [19:45] New connection established.
2013.08.10 [19:45] Connection closed after 0 request-response exchanges.
2013.08.10 [19:45] Block change detected due to long poll response
2013.08.10 [19:45] Long poll connection received block change notification
2013.08.10 [19:45] Server now building on top of a new block - ditching stale work
2013.08.10 [19:47] New connection established.
2013.08.10 [19:47] Connection closed after 19 request-response exchanges.
2013.08.10 [19:48] Connection closed after 3 request-response exchanges.
2013.08.10 [19:48] New connection established.
2013.08.10 [19:48] Block change detected due to long poll response
2013.08.10 [19:48] Long poll connection received block change notification
2013.08.10 [19:48] Server now building on top of a new block - ditching stale work
2013.08.10 [19:49] New connection established.
2013.08.10 [19:50] Connection closed after 0 request-response exchanges.
2013.08.10 [19:52] New connection established.
2013.08.10 [19:52] Connection timed out
2013.08.10 [19:52] Connection closed after 26 request-response exchanges.
2013.08.10 [19:52] Block change detected due to long poll response
2013.08.10 [19:52] Long poll connection received block change notification
2013.08.10 [19:52] Server now building on top of a new block - ditching stale work
2013.08.10 [19:54] Connection closed after 13 request-response exchanges.
2013.08.10 [19:54] New connection established.
2013.08.10 [19:54] New connection established.
2013.08.10 [19:55] Connection timed out
2013.08.10 [19:55] Connection closed after 4 request-response exchanges.
2013.08.10 [19:57] New connection established.
2013.08.10 [19:57] Connection closed after 38 request-response exchanges.
2013.08.10 [19:59] Block change detected due to long poll response
2013.08.10 [19:59] Long poll connection received block change notification
2013.08.10 [19:59] Server now building on top of a new block - ditching stale work
2013.08.10 [19:59] Block change detected due to long poll response
2013.08.10 [19:59] Long poll connection received block change notification
2013.08.10 [19:59] Server now building on top of a new block - ditching stale work
2013.08.10 [20:01] Connection closed after 15 request-response exchanges.
2013.08.10 [20:01] New connection established.
2013.08.10 [20:02] New connection established.
2013.08.10 [20:02] Block change detected due to long poll response
2013.08.10 [20:02] Long poll connection received block change notification
2013.08.10 [20:02] Server now building on top of a new block - ditching stale work
2013.08.10 [20:02] Connection closed after 9 request-response exchanges.
2013.08.10 [20:03] Connection closed after 4 request-response exchanges.
2013.08.10 [20:03] New connection established.
2013.08.10 [20:04] New connection established.
2013.08.10 [20:04] Connection timed out
2013.08.10 [20:04] Connection closed after 3 request-response exchanges.
2013.08.10 [20:05] Block change detected due to long poll response
2013.08.10 [20:05] Long poll connection received block change notification
2013.08.10 [20:05] Server now building on top of a new block - ditching stale work
2013.08.10 [20:06] Connection closed after 7 request-response exchanges.
2013.08.10 [20:06] New connection established.
2013.08.10 [20:07] Block change detected due to long poll response
2013.08.10 [20:07] Long poll connection received block change notification
2013.08.10 [20:07] Server now building on top of a new block - ditching stale work
2013.08.10 [20:07] New connection established.
2013.08.10 [20:08] Connection closed after 0 request-response exchanges.
2013.08.10 [20:08] Block change detected due to long poll response
2013.08.10 [20:08] Long poll connection received block change notification
2013.08.10 [20:08] Server now building on top of a new block - ditching stale work
2013.08.10 [20:09] Block change detected due to long poll response
2013.08.10 [20:09] Long poll connection received block change notification
2013.08.10 [20:09] Server now building on top of a new block - ditching stale work
2013.08.10 [20:10] Connection closed after 21 request-response exchanges.
2013.08.10 [20:10] New connection established.
2013.08.10 [20:13] New connection established.
2013.08.10 [20:13] Connection closed after 16 request-response exchanges.
2013.08.10 [20:14] Connection closed after 3 request-response exchanges.
2013.08.10 [20:14] Connection closed after 19 request-response exchanges.
2013.08.10 [20:14] New connection established.
2013.08.10 [20:14] New connection established.
2013.08.10 [20:18] Connection closed after 19 request-response exchanges.
2013.08.10 [20:18] New connection established.
2013.08.10 [20:19] Connection closed after 0 request-response exchanges.
2013.08.10 [20:19] New connection established.
2013.08.10 [20:20] Block change detected due to long poll response
2013.08.10 [20:20] Long poll connection received block change notification
2013.08.10 [20:20] Server now building on top of a new block - ditching stale work
2013.08.10 [20:21] Block change detected due to long poll response
2013.08.10 [20:21] Long poll connection received block change notification
2013.08.10 [20:21] Server now building on top of a new block - ditching stale work
2013.08.10 [20:21] New connection established.
2013.08.10 [20:22] Icarus (COM4) ERROR: Icarus (COM4) ran out of work. Idling...
2013.08.10 [20:22] Connection timed out
2013.08.10 [20:22] Connection closed after 15 request-response exchanges.
2013.08.10 [20:23] New connection established.
2013.08.10 [20:24] Connection timed out
2013.08.10 [20:24] Connection closed after 8 request-response exchanges.
2013.08.10 [20:24] Connection closed after 0 request-response exchanges.
2013.08.10 [20:24] New connection established.
2013.08.10 [20:24] Block change detected due to long poll response
2013.08.10 [20:24] Long poll connection received block change notification
2013.08.10 [20:24] Server now building on top of a new block - ditching stale work
2013.08.10 [20:25] New connection established.
2013.08.10 [20:26] Connection closed after 8 request-response exchanges.
2013.08.10 [20:28] Block change detected due to long poll response
2013.08.10 [20:28] Long poll connection received block change notification
2013.08.10 [20:28] Server now building on top of a new block - ditching stale work
2013.08.10 [20:29] Block change detected due to long poll response
2013.08.10 [20:29] Long poll connection received block change notification
2013.08.10 [20:29] Server now building on top of a new block - ditching stale work
2013.08.10 [20:31] New connection established.
2013.08.10 [20:31] Connection closed after 0 request-response exchanges.
2013.08.10 [20:34] New connection established.
2013.08.10 [20:34] Connection closed after 8 request-response exchanges.
2013.08.10 [20:35] Connection closed after 47 request-response exchanges.
2013.08.10 [20:35] New connection established.
2013.08.10 [20:36] New connection established.
2013.08.10 [20:37] Connection closed after 0 request-response exchanges.
2013.08.10 [20:37] New connection established.
2013.08.10 [20:38] Connection closed after 0 request-response exchanges.
2013.08.10 [20:38] New connection established.
2013.08.10 [20:39] Connection closed after 0 request-response exchanges.
2013.08.10 [20:39] New connection established.
2013.08.10 [20:39] Connection closed after 4 request-response exchanges.
2013.08.10 [20:40] New connection established.
2013.08.10 [20:40] Block change detected due to long poll response
2013.08.10 [20:40] Long poll connection received block change notification
2013.08.10 [20:40] Server now building on top of a new block - ditching stale work
2013.08.10 [20:41] Block change detected due to long poll response
2013.08.10 [20:41] Long poll connection received block change notification
2013.08.10 [20:41] Server now building on top of a new block - ditching stale work
2013.08.10 [20:41] Connection closed after 3 request-response exchanges.
2013.08.10 [20:42] New connection established.
2013.08.10 [20:43] Connection closed after 0 request-response exchanges.
2013.08.10 [20:43] Connection closed after 15 request-response exchanges.
2013.08.10 [20:43] New connection established.
2013.08.10 [20:44] New connection established.
2013.08.10 [20:45] Connection closed after 4 request-response exchanges.
2013.08.10 [20:46] Connection closed after 32 request-response exchanges.
2013.08.10 [20:46] New connection established.
2013.08.10 [20:48] Block change detected due to long poll response
2013.08.10 [20:48] Long poll connection received block change notification
2013.08.10 [20:48] Server now building on top of a new block - ditching stale work
2013.08.10 [20:49] Connection closed after 19 request-response exchanges.
2013.08.10 [20:49] New connection established.
2013.08.10 [20:50] Connection closed after 1 request-response exchanges.
2013.08.10 [20:50] New connection established.
2013.08.10 [20:50] New connection established.
2013.08.10 [20:51] Connection timed out
2013.08.10 [20:51] Connection closed after 3 request-response exchanges.
2013.08.10 [20:52] Block change detected due to long poll response
2013.08.10 [20:52] Long poll connection received block change notification
2013.08.10 [20:52] Server now building on top of a new block - ditching stale work
2013.08.10 [20:52] New connection established.
2013.08.10 [20:53] Connection closed after 15 request-response exchanges.
2013.08.10 [20:53] Connection closed after 2 request-response exchanges.
2013.08.10 [20:53] New connection established.
2013.08.10 [20:54] New connection established.
2013.08.10 [20:55] Connection closed after 0 request-response exchanges.
2013.08.10 [20:56] New connection established.
2013.08.10 [20:56] Connection closed after 13 request-response exchanges.
2013.08.10 [20:57] Connection closed after 12 request-response exchanges.
2013.08.10 [20:57] New connection established.
2013.08.10 [20:58] New connection established.
2013.08.10 [20:58] Block change detected due to new work ID
2013.08.10 [20:58] Server now building on top of a new block - ditching stale work
2013.08.10 [20:58] Block change detected due to long poll response
2013.08.10 [20:58] Long poll connection received block change notification
2013.08.10 [20:58] Server now building on top of a new block - ditching stale work
2013.08.10 [20:58] Connection closed after 7 request-response exchanges.
2013.08.10 [21:02] Connection closed after 21 request-response exchanges.
2013.08.10 [21:02] New connection established.
2013.08.10 [21:02] Block change detected due to long poll response
2013.08.10 [21:02] Long poll connection received block change notification
2013.08.10 [21:02] Server now building on top of a new block - ditching stale work
2013.08.10 [21:03] Connection closed after 7 request-response exchanges.
2013.08.10 [21:03] New connection established.
2013.08.10 [21:04] Connection closed after 2 request-response exchanges.
2013.08.10 [21:04] New connection established.
2013.08.10 [21:05] Block change detected due to long poll response
2013.08.10 [21:05] Long poll connection received block change notification
2013.08.10 [21:05] Server now building on top of a new block - ditching stale work
2013.08.10 [21:06] Connection closed after 11 request-response exchanges.
2013.08.10 [21:06] New connection established.
2013.08.10 [21:06] Block change detected due to long poll response
2013.08.10 [21:06] Long poll connection received block change notification
2013.08.10 [21:06] Server now building on top of a new block - ditching stale work
2013.08.10 [21:07] Connection closed after 2 request-response exchanges.
2013.08.10 [21:07] New connection established.
2013.08.10 [21:07] Block change detected due to long poll response
2013.08.10 [21:07] Long poll connection received block change notification
2013.08.10 [21:07] Server now building on top of a new block - ditching stale work
2013.08.10 [21:07] Block change detected due to long poll response
2013.08.10 [21:07] Long poll connection received block change notification
2013.08.10 [21:07] Server now building on top of a new block - ditching stale work
2013.08.10 [21:08] New connection established.
2013.08.10 [21:09] Connection closed after 13 request-response exchanges.
2013.08.10 [21:09] Block change detected due to long poll response
2013.08.10 [21:09] Long poll connection received block change notification
2013.08.10 [21:09] Server now building on top of a new block - ditching stale work
2013.08.10 [21:10] Block change detected due to long poll response
2013.08.10 [21:10] Long poll connection received block change notification
2013.08.10 [21:10] Server now building on top of a new block - ditching stale work
2013.08.10 [21:11] Connection closed after 10 request-response exchanges.
2013.08.10 [21:11] New connection established.
2013.08.10 [21:11] New connection established.
2013.08.10 [21:12] Connection closed after 0 request-response exchanges.
2013.08.10 [21:13] Connection closed after 14 request-response exchanges.
2013.08.10 [21:14] New connection established.
2013.08.10 [21:14] New connection established.
2013.08.10 [21:14] Connection timed out
2013.08.10 [21:14] Connection closed after 2 request-response exchanges.
2013.08.10 [21:14] New connection established.
2013.08.10 [21:15] Connection closed after 11 request-response exchanges.
2013.08.10 [21:15] Connection timed out
2013.08.10 [21:15] Connection closed after 5 request-response exchanges.
2013.08.10 [21:15] New connection established.
2013.08.10 [21:15] New connection established.
2013.08.10 [21:16] Connection closed after 3 request-response exchanges.
2013.08.10 [21:16] Block change detected due to long poll response
2013.08.10 [21:16] Long poll connection received block change notification
2013.08.10 [21:16] Server now building on top of a new block - ditching stale work
2013.08.10 [21:19] Connection closed after 23 request-response exchanges.
2013.08.10 [21:19] New connection established.
2013.08.10 [21:20] Connection closed after 4 request-response exchanges.
2013.08.10 [21:20] New connection established.
2013.08.10 [21:21] Connection closed after 3 request-response exchanges.
2013.08.10 [21:22] New connection established.
2013.08.10 [21:22] New connection established.
2013.08.10 [21:23] Connection closed after 0 request-response exchanges.
2013.08.10 [21:26] Connection closed after 23 request-response exchanges.
2013.08.10 [21:26] New connection established.
2013.08.10 [21:26] Connection closed after 8 request-response exchanges.
2013.08.10 [21:27] New connection established.
2013.08.10 [21:28] New connection established.
2013.08.10 [21:28] Connection closed after 1 request-response exchanges.
2013.08.10 [21:29] Connection closed after 16 request-response exchanges.
2013.08.10 [21:29] New connection established.
2013.08.10 [21:30] New connection established.
2013.08.10 [21:30] Connection closed after 3 request-response exchanges.
2013.08.10 [21:30] Connection closed after 1 request-response exchanges.
2013.08.10 [21:31] New connection established.
2013.08.10 [21:31] Connection closed after 1 request-response exchanges.
2013.08.10 [21:32] New connection established.
2013.08.10 [21:32] New connection established.
2013.08.10 [21:32] Connection timed out
2013.08.10 [21:32] Connection closed after 1 request-response exchanges.
2013.08.10 [21:33] New connection established.
2013.08.10 [21:33] Connection closed after 9 request-response exchanges.
2013.08.10 [21:36] New connection established.
2013.08.10 [21:36] Connection closed after 0 request-response exchanges.
2013.08.10 [21:36] Connection closed after 2 request-response exchanges.
2013.08.10 [21:36] New connection established.
2013.08.10 [21:38] New connection established.
2013.08.10 [21:38] Connection timed out
2013.08.10 [21:38] Connection closed after 4 request-response exchanges.
2013.08.10 [21:39] Block change detected due to long poll response
2013.08.10 [21:39] Long poll connection received block change notification
2013.08.10 [21:39] Server now building on top of a new block - ditching stale work
2013.08.10 [21:40] Connection closed after 19 request-response exchanges.
2013.08.10 [21:40] New connection established.
2013.08.10 [21:42] Block change detected due to long poll response
2013.08.10 [21:42] Long poll connection received block change notification
2013.08.10 [21:42] Server now building on top of a new block - ditching stale work
2013.08.10 [21:43] New connection established.
2013.08.10 [21:44] Connection closed after 17 request-response exchanges.
2013.08.10 [21:44] New connection established.
2013.08.10 [21:45] Block change detected due to long poll response
2013.08.10 [21:45] Long poll connection received block change notification
2013.08.10 [21:45] Server now building on top of a new block - ditching stale work
2013.08.10 [21:46] Connection closed after 9 request-response exchanges.
2013.08.10 [21:46] Connection closed after 6 request-response exchanges.
2013.08.10 [21:46] New connection established.
2013.08.10 [21:46] New connection established.
2013.08.10 [21:47] Connection closed after 2 request-response exchanges.
2013.08.10 [21:48] Block change detected due to long poll response
2013.08.10 [21:48] Long poll connection received block change notification
2013.08.10 [21:48] Server now building on top of a new block - ditching stale work
2013.08.10 [21:51] New connection established.
2013.08.10 [21:51] Connection closed after 27 request-response exchanges.
2013.08.10 [21:51] New connection established.
2013.08.10 [21:53] Connection closed after 26 request-response exchanges.
2013.08.10 [21:53] Connection closed after 12 request-response exchanges.
2013.08.10 [21:53] New connection established.
2013.08.10 [21:55] New connection established.
2013.08.10 [21:55] Connection closed after 15 request-response exchanges.
2013.08.10 [21:56] Connection closed after 7 request-response exchanges.
2013.08.10 [21:57] New connection established.
2013.08.10 [21:57] New connection established.
2013.08.10 [21:57] Block change detected due to long poll response
2013.08.10 [21:57] Long poll connection received block change notification
2013.08.10 [21:57] Server now building on top of a new block - ditching stale work
2013.08.10 [21:57] Block change detected due to long poll response
2013.08.10 [21:57] Long poll connection received block change notification
2013.08.10 [21:57] Server now building on top of a new block - ditching stale work
2013.08.10 [21:57] Connection closed after 0 request-response exchanges.
2013.08.10 [21:57] Connection timed out
2013.08.10 [21:57] Connection closed after 2 request-response exchanges.
2013.08.10 [21:57] New connection established.
2013.08.10 [21:58] Block change detected due to long poll response
2013.08.10 [21:58] Long poll connection received block change notification
2013.08.10 [21:58] Server now building on top of a new block - ditching stale work
2013.08.10 [21:58] Block change detected due to long poll response
2013.08.10 [21:58] Long poll connection received block change notification
2013.08.10 [21:58] Server now building on top of a new block - ditching stale work
2013.08.10 [21:59] Block change detected due to long poll response
2013.08.10 [21:59] Long poll connection received block change notification
2013.08.10 [21:59] Server now building on top of a new block - ditching stale work
2013.08.10 [21:59] Block change detected due to new work ID
2013.08.10 [21:59] Server now building on top of a new block - ditching stale work
2013.08.10 [21:59] Block change detected due to long poll response
2013.08.10 [21:59] Long poll connection received block change notification
2013.08.10 [21:59] Server now building on top of a new block - ditching stale work
2013.08.10 [22:00] Block change detected due to long poll response
2013.08.10 [22:00] Long poll connection received block change notification
2013.08.10 [22:00] Server now building on top of a new block - ditching stale work
2013.08.10 [22:00] Block change detected due to long poll response
2013.08.10 [22:00] Long poll connection received block change notification
2013.08.10 [22:00] Server now building on top of a new block - ditching stale work
2013.08.10 [22:00] New connection established.
2013.08.10 [22:00] Connection closed after 16 request-response exchanges.
2013.08.10 [22:01] New connection established.
2013.08.10 [22:02] Connection closed after 7 request-response exchanges.
2013.08.10 [22:02] Block change detected due to long poll response
2013.08.10 [22:02] Long poll connection received block change notification
2013.08.10 [22:02] Server now building on top of a new block - ditching stale work
2013.08.10 [22:02] Block change detected due to long poll response
2013.08.10 [22:02] Long poll connection received block change notification
2013.08.10 [22:02] Server now building on top of a new block - ditching stale work
2013.08.10 [22:03] New connection established.
2013.08.10 [22:04] Connection closed after 0 request-response exchanges.
2013.08.10 [22:07] Connection closed after 32 request-response exchanges.
2013.08.10 [22:07] New connection established.
2013.08.10 [22:07] Connection closed after 23 request-response exchanges.
2013.08.10 [22:07] Block change detected due to long poll response
2013.08.10 [22:07] Long poll connection received block change notification
2013.08.10 [22:07] Server now building on top of a new block - ditching stale work
2013.08.10 [22:07] New connection established.
2013.08.10 [22:07] Block change detected due to long poll response
2013.08.10 [22:07] Long poll connection received block change notification
2013.08.10 [22:07] Server now building on top of a new block - ditching stale work
2013.08.10 [22:09] New connection established.
2013.08.10 [22:10] Connection closed after 9 request-response exchanges.
2013.08.10 [22:11] Block change detected due to long poll response
2013.08.10 [22:11] Long poll connection received block change notification
2013.08.10 [22:11] Server now building on top of a new block - ditching stale work
2013.08.10 [22:14] Connection closed after 25 request-response exchanges.
2013.08.10 [22:14] New connection established.
2013.08.10 [22:15] New connection established.
2013.08.10 [22:15] Block change detected due to long poll response
2013.08.10 [22:15] Long poll connection received block change notification
2013.08.10 [22:15] Server now building on top of a new block - ditching stale work
2013.08.10 [22:15] Block change detected due to new work ID
2013.08.10 [22:15] Server now building on top of a new block - ditching stale work
2013.08.10 [22:15] Block change detected due to long poll response
2013.08.10 [22:15] Long poll connection received block change notification
2013.08.10 [22:15] Server now building on top of a new block - ditching stale work
2013.08.10 [22:15] Connection closed after 0 request-response exchanges.
2013.08.10 [22:15] New connection established.
2013.08.10 [22:16] Connection closed after 0 request-response exchanges.
2013.08.10 [22:17] Block change detected due to long poll response
2013.08.10 [22:17] Long poll connection received block change notification
2013.08.10 [22:17] Server now building on top of a new block - ditching stale work
2013.08.10 [22:18] Connection closed after 19 request-response exchanges.
2013.08.10 [22:18] New connection established.
2013.08.10 [22:18] New connection established.
2013.08.10 [22:18] Block change detected due to long poll response
2013.08.10 [22:18] Long poll connection received block change notification
2013.08.10 [22:18] Server now building on top of a new block - ditching stale work
2013.08.10 [22:18] Block change detected due to long poll response
2013.08.10 [22:18] Long poll connection received block change notification
2013.08.10 [22:18] Server now building on top of a new block - ditching stale work
2013.08.10 [22:18] Work rejected. Server says: Stale proof of work
2013.08.10 [22:19] Connection closed after 1 request-response exchanges.
2013.08.10 [22:19] Connection closed after 9 request-response exchanges.
2013.08.10 [22:19] New connection established.
2013.08.10 [22:20] Work rejected. Server says: Stale proof of work
2013.08.10 [22:20] Block change detected due to long poll response
2013.08.10 [22:20] Long poll connection received block change notification
2013.08.10 [22:20] Server now building on top of a new block - ditching stale work
2013.08.10 [22:20] New connection established.
2013.08.10 [22:20] Connection closed after 7 request-response exchanges.
2013.08.10 [22:21] Connection closed after 5 request-response exchanges.
2013.08.10 [22:21] New connection established.
2013.08.10 [22:22] Block change detected due to long poll response
2013.08.10 [22:22] Long poll connection received block change notification
2013.08.10 [22:22] Server now building on top of a new block - ditching stale work
2013.08.10 [22:23] New connection established.
2013.08.10 [22:24] Connection closed after 12 request-response exchanges.
2013.08.10 [22:24] Connection timed out
2013.08.10 [22:24] Connection closed after 2 request-response exchanges.
2013.08.10 [22:24] New connection established.
2013.08.10 [22:25] New connection established.
2013.08.10 [22:25] Block change detected due to long poll response
2013.08.10 [22:25] Long poll connection received block change notification
2013.08.10 [22:25] Server now building on top of a new block - ditching stale work
2013.08.10 [22:26] Connection closed after 12 request-response exchanges.
2013.08.10 [22:26] Connection closed after 1 request-response exchanges.
2013.08.10 [22:27] New connection established.
2013.08.10 [22:27] New connection established.
2013.08.10 [22:28] Connection closed after 2 request-response exchanges.
2013.08.10 [22:28] Connection closed after 4 request-response exchanges.
2013.08.10 [22:28] New connection established.
2013.08.10 [22:29] New connection established.
2013.08.10 [22:29] Block change detected due to long poll response
2013.08.10 [22:29] Long poll connection received block change notification
2013.08.10 [22:29] Server now building on top of a new block - ditching stale work
2013.08.10 [22:30] Connection closed after 0 request-response exchanges.
2013.08.10 [22:30] Block change detected due to long poll response
2013.08.10 [22:30] Long poll connection received block change notification
2013.08.10 [22:30] Server now building on top of a new block - ditching stale work
2013.08.10 [22:30] Block change detected due to long poll response
2013.08.10 [22:30] Long poll connection received block change notification
2013.08.10 [22:30] Server now building on top of a new block - ditching stale work
2013.08.10 [22:30] New connection established.
2013.08.10 [22:31] Connection closed after 0 request-response exchanges.
2013.08.10 [22:31] Connection closed after 20 request-response exchanges.
2013.08.10 [22:32] New connection established.
2013.08.10 [22:32] New connection established.
2013.08.10 [22:33] Connection timed out
2013.08.10 [22:33] Connection closed after 4 request-response exchanges.
2013.08.10 [22:34] New connection established.
2013.08.10 [22:35] Connection closed after 16 request-response exchanges.
2013.08.10 [22:35] Connection closed after 11 request-response exchanges.
2013.08.10 [22:35] New connection established.
2013.08.10 [22:37] Block change detected due to long poll response
2013.08.10 [22:37] Long poll connection received block change notification
2013.08.10 [22:37] Server now building on top of a new block - ditching stale work
2013.08.10 [22:37] Block change detected due to long poll response
2013.08.10 [22:37] Long poll connection received block change notification
2013.08.10 [22:37] Server now building on top of a new block - ditching stale work
2013.08.10 [22:39] Block change detected due to long poll response
2013.08.10 [22:39] Long poll connection received block change notification
2013.08.10 [22:39] Server now building on top of a new block - ditching stale work
2013.08.10 [22:40] Connection closed after 28 request-response exchanges.
2013.08.10 [22:40] New connection established.
2013.08.10 [22:41] Block change detected due to long poll response
2013.08.10 [22:41] Long poll connection received block change notification
2013.08.10 [22:41] Server now building on top of a new block - ditching stale work
2013.08.10 [22:42] Block change detected due to long poll response
2013.08.10 [22:42] Long poll connection received block change notification
2013.08.10 [22:42] Server now building on top of a new block - ditching stale work
2013.08.10 [22:42] Block change detected due to long poll response
2013.08.10 [22:42] Long poll connection received block change notification
2013.08.10 [22:42] Server now building on top of a new block - ditching stale work
2013.08.10 [22:42] Work rejected. Server says: Stale proof of work
2013.08.10 [22:42] New connection established.
2013.08.10 [22:42] Connection closed after 13 request-response exchanges.
2013.08.10 [22:43] Connection closed after 8 request-response exchanges.
2013.08.10 [22:43] Block change detected due to long poll response
2013.08.10 [22:43] Long poll connection received block change notification
2013.08.10 [22:43] Server now building on top of a new block - ditching stale work
2013.08.10 [22:43] New connection established.
2013.08.10 [22:43] Block change detected due to long poll response
2013.08.10 [22:43] Long poll connection received block change notification
2013.08.10 [22:43] Server now building on top of a new block - ditching stale work
Thanks for the response. Just looking for a bit more education.
My understanding is that it is mostly luck that determines whether we build a new block.
My understanding is that it is mostly luck that determines whether we build a new block.
The more hashrate the better the chance to get blocks. With a high hashrate pool you get several blocks per day, which means several small payments to you as a miner. Mining solo or in a tiny pool it might take months or even years of nothing before you got a big payment. Most miners prefer the low variance with frequent small payments.
Why does the Bitminter client acceleratometer still show 0.00 after 7 days of mining?
I do get the coins added to my account.
I do get the coins added to my account.
Must be a bug. I see your Icarus/block erupter shows a hashrate, but the total hashrate is still zero. I haven't seen this happening myself, so I'm not sure what would cause it.
This problem is still recurring with me. I hope you can fix it.
Are there any log messages when this happens? That's the text area at the bottom.
Do accepted proofs of work still go up (the yellow boxes)? Or is everything just stuck, like the erupter hashrate staying at the exact same number instead of going slightly up and down like usual?
Why does the Bitminter client acceleratometer still show 0.00 after 7 days of mining?
I do get the coins added to my account.
I do get the coins added to my account.
Must be a bug. I see your Icarus/block erupter shows a hashrate, but the total hashrate is still zero. I haven't seen this happening myself, so I'm not sure what would cause it.
This problem is still recurring with me. I hope you can fix it.
Thanks for the response. Just looking for a bit more education.
My understanding is that it is mostly luck that determines whether we build a new block.
That being said, more is better. It is like buying lottery tickets. The more you buy the better your chances of winning.
But, I wouldn't spend a million to win a million.
I am going to keep watching the blocks created and see if we improve as more of the larger rigs get online.
I have more ordered myself. But nothing over 100 Ghz.
Thanks
My understanding is that it is mostly luck that determines whether we build a new block.
That being said, more is better. It is like buying lottery tickets. The more you buy the better your chances of winning.
But, I wouldn't spend a million to win a million.
I am going to keep watching the blocks created and see if we improve as more of the larger rigs get online.
I have more ordered myself. But nothing over 100 Ghz.
Thanks
Hi
Great job with the pool and the mining software.
I wonder if any thought has been given to a tiered approach to the pool. In other words, have a pool for the really big guys and another for us smaller folks.
I figure it is worth a thought given that there is no way we can keep up with guys running 2 Thz.
Just opening for discussion.
Great job with the pool and the mining software.
I wonder if any thought has been given to a tiered approach to the pool. In other words, have a pool for the really big guys and another for us smaller folks.
I figure it is worth a thought given that there is no way we can keep up with guys running 2 Thz.
Just opening for discussion.
Hi,
nice to hear that you like the pool and miner
The really big guys are helping reduce variance for you. You don't need to "keep up" with other miners in the same pool. But you do need to keep up with the global hashrate if you don't want your mining income to drop as the difficulty rises.
I'd see it this way.. massive ASIC production causing the difficulty to skyrocket is bad for your mining income. But having a decent share of the global hashpower in our pool is good as it reduces variance.
If you want a lot of variance (which you would get in a pool with only small miners) then you could try solo mining. I wouldn't recommend it though. You could be waiting a year or two before you get anything at all.
Hi
Great job with the pool and the mining software.
I wonder if any thought has been given to a tiered approach to the pool. In other words, have a pool for the really big guys and another for us smaller folks.
I figure it is worth a thought given that there is no way we can keep up with guys running 2 Thz.
Just opening for discussion.
Great job with the pool and the mining software.
I wonder if any thought has been given to a tiered approach to the pool. In other words, have a pool for the really big guys and another for us smaller folks.
I figure it is worth a thought given that there is no way we can keep up with guys running 2 Thz.
Just opening for discussion.
What aspect of the pool or mining exactly are you wanting to "tier" based on hash rate?
Hi
Great job with the pool and the mining software.
I wonder if any thought has been given to a tiered approach to the pool. In other words, have a pool for the really big guys and another for us smaller folks.
I figure it is worth a thought given that there is no way we can keep up with guys running 2 Thz.
Just opening for discussion.
Great job with the pool and the mining software.
I wonder if any thought has been given to a tiered approach to the pool. In other words, have a pool for the really big guys and another for us smaller folks.
I figure it is worth a thought given that there is no way we can keep up with guys running 2 Thz.
Just opening for discussion.
Will the bitminter client ever be adapted to work with litecoin or feathercoin?
Don't know yet, sorry.
Will the bitminter client ever be adapted to work with litecoin or feathercoin?
I understand this is probably not where I'm supposed to post, But I got my miners set up, I have a worker set up and my wallet key set, but I don't seem to be mining any coins or even getting payouts.. what gives? Am I missing something?
Are you getting accepted proofs of work? Shown in the client and under "my account" -> "workers" on the website. If so, then all is fine.
How payouts work:
Some payment info:
The approximate mint speed shown in BitMinter client is just that, an approximation. Bitcoin mining is like a lottery. How often we find a block, and earn bitcoins from that block, is random. Each hash you process is like a lottery ticket. Each hash has a (very low) chance of producing a block. You get paid with coins from a block whenever a block is found by someone mining in the pool. Your share of the income from a block is determined by the amount of work that you did in the most recent 10 shifts at the time the block is found.
Because of this, your daily income will vary with luck. That's often referred to as variance. There may also be some hours between two payouts if we are having bad luck and no blocks are found for a while.
In addition to that there is a delay from the time you do some work until that work is fully paid. The work you do is registered in a shift, and then that work is credited with income from new blocks we find until its shift is no longer among the 10 latest shifts. This takes a few hours. If you turn off the prepay perk then there is an additional delay having to wait for blocks to confirm, which takes about 20 hours.
So, assuming you have prepay on, if you do 24 hours of work and then look at the results, then only some of that work has been fully paid. The remaining work is still receiving pay, even if you stop mining. Needless to say that is not going to look very profitable, when you are looking at all the work you did but only part of the pay you are going to receive.
Comparing pools by how much you get paid for 24 hours of mining is pointless. The comparison becomes "which pool has the best luck today?" You can't use that data for anything. The luck a pool has today has no influence on its luck tomorrow. Believing that it does is called "gambler's fallacy" which you can ready about on wikipedia:
http://en.wikipedia.org/wiki/Gambler%27s_fallacy
If you want to know how BitMinter's payouts have been over time you can read Organofcorti's very detailed analysis here:
http://organofcorti.blogspot.com/2013/05/131-bitminter-and-luck.html
I understand this is probably not where I'm supposed to post, But I got my miners set up, I have a worker set up and my wallet key set, but I don't seem to be mining any coins or even getting payouts.. what gives? Am I missing something?
Why does the Bitminter client acceleratometer still show 0.00 after 7 days of mining?
I do get the coins added to my account.
I do get the coins added to my account.
Must be a bug. I see your Icarus/block erupter shows a hashrate, but the total hashrate is still zero. I haven't seen this happening myself, so I'm not sure what would cause it.
Why does the Bitminter client acceleratometer still show 0.00 after 7 days of mining?
I do get the coins added to my account.
I do get the coins added to my account.
I'm currently running this with no anti virus and it's working ok but I'd like to have something compatible it there is something.
I'm setting up this account in preparations for some more serious hardware but am currently mining with an old video card. The miner says I'm doing 20 mh/s but the dial still show's zero. This may be normal with such a slow card but It would be nice if you could reassure me of this.
Also the performance for the card shows I should be mining 0.0003 bitcoins/day but the overall performance is showing zero.
Microsoft Security Essentials is an ok free antivirus. It at least doesn't bug you with popups to buy a full version or anything, and it works fine with BitMinter. I'm setting up this account in preparations for some more serious hardware but am currently mining with an old video card. The miner says I'm doing 20 mh/s but the dial still show's zero. This may be normal with such a slow card but It would be nice if you could reassure me of this.
Also the performance for the card shows I should be mining 0.0003 bitcoins/day but the overall performance is showing zero.
Jump to: