Mining service restart... will only take a second or two.

w00t, back on.

edit: very briefly and bounced off again...

Though bfg showing a network failure that bounced it to next failover pool so might not have been bitminter... but I'm fed up of messing with it now, it can go back to bitminter if it feels like it later.

We haven't really had many "average" days lately, we were super lucky on the 23rd, but have been unlucky since... I THINK we're doing about 8 blocks a day average, and at a little under 200Gh I'm getting about 0.01 a block, so 600 should be getting a little over 0.03ish and about a quarter coin a day on average.

How difficulty increases affect your mining income:

http://bitcoin.stackexchange.com/questions/16526/how-does-a-difficulty-increase-affect-a-miners-income


Let me know if you find out whether it works with the latest Bitminter client or not.

Thanks Dr H, keep at it ... ... ...

http://www.youtube.com/watch?v=NYGjjrMcgps

Are there still issues? I am trying to connect a stratum pool. It will work for about 10 mins then workers shows 0 and full size stats shows a missing box even though the mining_proxy.py shows activity. Later on it might start working again then it repeats with zero activity.

Is there something wrong with the pool, my Avalon's aren't hashing from your pool, they are set to hash from you first and failover in the event your pools stop working?

Wow, 4 blocks in a row on the blockchain today.

Everything should be running smoothly now. If you have issues there are two types of IP based filtering in use. There's a botnet ban list where IPs sit for some time. And then there is the anti ddos which may accidentally filter you along with attackers during an attack. We're working to improve on this. This should only last a few minutes before you can mine again though. If you are unable to mine for hours then you could be on the botnet ban list, or it could be a different issue entirely. In that case use the contact form ("contact" menu) on the website and I'll see if I can figure out what the problem is.


Hehe, this gave me a good laugh. That's exactly what it's like.

Stats seem odd as well.  New to the pool, but it usually seems to average ~450T and ~1200 workers.  Right now we are at ~340T and ~7800 workers.

Chainminer-Bitfury-DDoS note:
You may have to manually generate and modify a best.cnf in order to turn off auto-tuning for your chips.  Normally, you would want this on.  But, when the pool gets nailed, Chainminer seems to want to down-clock entire banks of chips.  And, they may not return to normal after the DDoS subsides.

Chips will start off hashing very slowly until they warm up if the clock rate is manually set too high.

I originally posted this in the miner thread, but then realized that thread was specific to the Bitminter Java client.  That post has been deleted.