DDoS attack is starting up again.

Mining service is back online again.

I am working on getting backup pools in the client, multiple mining servers, and some other things that will help.

No, reducing the global hashrate doesn't have any immediate impact, as the difficulty is still the same.

Your chance to make blocks is only affected by your own hashrate and the current difficulty.

If they ddos a substantial amount of the global hashrate for a substantial amount of time then it may affect the next difficulty adjustment. You would have to ddos a lot to have any noticeable effect. Doesn't seem to be a likely reason for the attacks, unless the attackers are confused about how difficulty works.

Confirmed, it's a DDoS attack.

Something like 90% packetloss to the mining server right now. Could be a DDoS attack.

Could be a power issue, yes.

I guess the best thing to do is; find out which hubs are used by people mining with 50 of those sticks. Buy the same hub.

So different miner clients, different USB ports, different USB hubs, all result in lots of errors..

I guess you could try them on a different computer, but it sounds like the devices themselves are having issues. Are they overclocked? Do they get very hot?

Does it make any difference if you just try to run 1 or 2 instead of so many at once?

That's a lot of errors. Could it be an issue with the USB hub? Have you tried whether it works with bfgminer?

BitMinter client v1.4.0 beta2 is ready for testing.

New since beta1:

• Corrected hashrate and runs smoother on ASICMiner Block Erupter USB
• Fixed intermittent error messages on BFL ASICs
• Better Mac OS X integration (proper screen menu and dock icon)

Please check it out:

I agree. Changing the algorithm just means new ASICs will be made for the new algorithm. It doesn't really change anything.

He does have a point about "one dude" though.

These guys seem to be spamming heavily by email, various forums and even a debian mailing list.

I guess the "advertising" has begun.

If someone accuses you of being a scammer, the answer is not to start spamming everywhere. That's something scammers do.

I guess it drops to 0 for a short moment when there is a block change (long poll). Maybe I made the code for the Icarus a bit too sensitive to that and it complains quickly.

I'll add Stratum support soon, which will eliminate that moment of rushing to get new work after a block change.

If it works ok it will become the next beta, and hopefully soon the final 1.4.0.

Hmm, is the status line at the bottom showing zero queued work at the time? (grey boxes)

For those wondering if CloudHashing is getting ASICs from other places than BFL, the second banner in the rotation at https://www.kncminer.com/ can be interesting.

Could you cut'n'paste the messages and PM them to me here, or email at operator@bitminter.com ?

Any info on which protocol they use? If they need a computer with miner software to run, that is.

They will run fine with the pool. But probably not with BitMinter client, depending on which protocol they use.

Does it help to move it to a different USB port? If you mine on only that device does that work?


Did you try mining on only that one, connected directly to the computer instead of the hub? Just to rule out the hub being bad.

You could also try a different miner (I believe bfgminer works with the silabs driver), but the way it finds the wrong nonces all the time, it doesn't look good.

At the Bitcoin 2013 conference, security researcher Dan Kaminsky predicted that the current algorithm will not survive the year.

All I've been able to find out is that they will create their own protocol and support will be added to cgminer. I've offered to add support in BitMinter client, but they're not very communicative.