:: UPDATE on the forking issues ::

One major pool never updated their client. They are on a fork that started when the majority kicked in. We have contacted them but not had a reply as of this writing. This looks like what is keeping the forked chain alive.

There is a more recent fork from another pool that we believe updated. We have contacted them also and are awaiting a reply. This does not appear malicious, but we're a bit baffled by it.

We have been gathering data from the network to see how much real effect these have had on the network and the block chain. As of right now, the majority of clients on 0.10.4.0 ( around 98%) that we can see from our nodes are reporting the correct block height. The other 0.10.4.0 clients appear not to be on a forked chain, but in the process of syncing.

Please check your clients and compare the blockheights to http://be2.sexcoin.info.

Clients on 0.6.4.6 appear to be most affected.

I will keep you informed as we find out more.