Some questions tied to speculative thoughts on the attack.

When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?

Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.

To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?

Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.

Happy to delete this post if you think it just promotes unnecessary FUD.

I have the similar thought

What's the status of XMR's collaboration with i2p?

Still can't sync   It's been a while now... should have been sorted out by now?

Ongoing, we've formed a working group with i2p, Abscond, i2pd, and Anoncoin, called Privacy Solutions. i2pd is reaching a level of working-ness that should allow us to start integrating it soon. Given the number of moving parts it's extremely hard to put a timeframe on it.

Get the latest binary off the OP and try again

Edit: and delete your p2pstate.bin and poolstate.bin, your p2pstate.bin is definitely corrupt.

Interesting how stable the prize is, considering the delays.

I believe this to be the increased confidence in the devs. They have shown to be consistent in their delivery and extremely fast in reacting to any major issues. They have remained professional and to investors this is a huge plus. There are other factors but for me this is one of the coins I hold without worry.

Ok - Windows blockchain has been updated with one that is synced up past the fork correctly -

http://monero.cc/downloads/blockchain/win/blockchain.bin
sha: 8c23da70c1291a61444090d8d5127dd6c12efa81

We won't update that blockchain for a few days, although when it updates once the patch is fully tested and deployed that sha will obviously change:)

Thanks for your patience!