Hey guys, turbulent night, but let me explain exactly what happened. We had uploaded the updated clients, which actually prevent the coin from forking, but not everyone upgraded, or if people upgraded, they didn’t wipe out their previous block chain, and kept hashing on the old chain.
It seems, that a pool, although upgraded their wallet, they did not remove and refresh their block chain information, and were therefore hashing on the wrong chain. This caused a lot of problems for us, because the pool started re-broadcasting the wrong block chain to people, and this caused a chain effect of bad blockhains being broadcast. This caused a domino effect, as new people who were downloading the client, were saturated with bad block chain information, and then re-distributing it.
Now, in regards to the Hashharder stuff, and the reason we “picked” their chain. First of all, no chain was “picked” as there was no wallet update— we don’t magically get to decide which chain is the official one. The chain that Hashharder was using, was also the same chain that our Seeders were seeding, and all of our machines were using, as well as what was hardcoded in to the client, not to mention the chain was about 6-700 blocks ahead of the other one, and as you know, the longest chain always wins.
We are working today to bring more seed nodes online, and increasing the capacity of our current seed servers as well as seeing what we can do to improve the stability of the coin via wallet updates.
Lead Dev I/O Coin
That actually makes sense. Thank you for the explanation.
^ 
