A short update from us.

We have decided to ban a user that previously has caused us trouble mining via larger botnets and/or a proxy-pool. I let him back in and even compensated him for the inconvenience back then.
He's was now using ~25-30 connections via TOR to hide his activity this time, we've been in contact with him and informed him about the situation. The amount of getworks was totally of the charts to, our environment can't handle spikes from a few hundred getworks/s to multiple thousands over a short period of time. Directly comparable with the "slashdot-effect".

Bandwidth wise it's a jump from about 1MB/s to 8-9MB/s during the hops - it's a pretty massive change.

He's the one responsible for the HUGE increase in hash rate right after new rounds (~800gh hopper, my guess it's some of the pool-hopping-proxys, maybe not ABCPool this time tho).
He's also the one responsible for the lowered efficiency during those rounds and connections troubles we've gotten reports for over the past days.

The payment issues (Insufficient funds error) should be resolved now, permanently. We've taken some actions to make it possible for us to access the cold-stored funds easier without making it a security risk.
Better safe then sorry!

PPLNS is still a top priority, to solve the "hopper problem" permanently.
I cannot express in words how I'm sorry I am for all the delays for that.

We've going to focus on that for the entire next week, you have my word on that.
If you have any questions, don't hesitate to contact us!

--
Regards, Jim
Bit LC Inc.
https://www.bitlc.net/