Quote from: Roland68 on May 23, 2013, 08:00:54 AM

It looks like it was a bug in Bitcoin software ... see message from slush pool "21.05.2013
Bug in bitcoind caused many invalid blocks generated in recent hours. Thanks to cooperation with bitcoin developers, a bugfix has been deployed. Pool is now back in normal operation."

You just burned electric power for nothing ...

This is also the problem of the Pool managers (generally young people ...) They roll rapidly new software build and forget the good old sentence (if it's not broken, don't fix it)

the old programmer.

As I understand it, the issue was high CPU usage on bitcoind leading to invalid *shares*, not actually invalid *blocks*. Or was there another issue I missed? Here's slush's post from the slush pool thread:

Quote from: slush on May 21, 2013, 06:18:53 PM

I've detected problems in bitcoind 0.8.1 where high number of transactions in memory pool caused 100% CPU load on the pool server. Because of this, submitting of new blocks were delayed for tens of seconds and caused high invalid rate.

Sipa (the bitcoin developer) implemented fix for this problem (https://github.com/bitcoin/bitcoin/pull/2677) which I just tested and implemented to the pool server. I'm watching the pool closely, but the CPU load dropped from 100% back to 2-3%, so everything looks fine so far...