Quote from: MrBrew on July 14, 2014, 07:34:45 PM

Quote from: MrData on July 14, 2014, 02:24:24 PM

The bad blocks are probably still floating around the network yeah, I don't think anyone is actively trying to mess with it anymore. Just as a test I've resynced v1 a couple of times but I can't get it to crash or anything.

Quote from: cuke on July 14, 2014, 07:59:36 AM

Built the new v1 source successfully. During the new sync, everything goes well for a few minutes then sync stops and memory usage climbs until eventually the app quits. Restarting just repeats the same. Needed a few restarts to get the full sync. I noticed this yesterday (memory usage) when my coinswap was delayed.

Could this be a sign that the attack is ongoing.

I got around 2000 WAS during the attack I won't try to redeem them.

I was getting blocks with 300 WAS during the attack. I upgraded to the latest client and getting 0 WAS again.

Did they actually make it into the blockchain? The v1 client even pre-patch should have rejected any >0 reward blocks (assuming it was running 0.8.99.9), especially when it was back on the right side of the hardfork.