It should have stopped at block 9323 saying it isn't synced. That is because there hasn't been a block found in several days. We are working to solve a new block now to put it back in sync. addnode=199.180.115.125
There is no risk in testing the client from another computer. But, your loss. There is a pool that has reviewed the code and is agreeing to post a new pool to set the chain in place and unfreeze it. Nobody's transactions or money will be lost!
@Magnet I am being 100% legitimate. Download the client and check it out. Nothing drastic changed no forks nothing but a manual retarget after block 9323
I am releasing a client that I am sure everyone will agree with including Russ. I will be posting the source files of the files I have changed. The goal will be a manual retarget and updated retarget times to prevent future flash mining. I have repaired Bottlecaps with a similar method. The client will be posted here soon. IT IS YOUR CHOICE TO USE THE CLIENT! I am not trying to trick anybody as this is the actual block chain and none of your money will be lost!
You must use a program to change all the windows breaklines with a unix breakline. Also make sure you use the git command as it might also automatically do that for you. Do not download the .zip as that will most likely not work.
I have done an intense investigation on this. I have come to the conclusion that two network nodes had lost connection and subsequently caused the network to fork. The issue has been resolved by the follow. We have reached the best fit approach that will keep the value of this coin high by going towards the cryptsy chain. The cryptsy chain had a connection directly to both of my nodes at the time of the accident of which had 21 connections not including the two pools that were operating on other nodes at the current time. The banscore of my nodes had been triggered by orphans being submitted so the pools left my nodes.
So therefore I have come to the conclusion that the cryptsy chain is the main blockchain and the others are forks. I found a total of 4 forks that occured around the time of the incident. All have been removed and there is only one chain existing now.
To address this issue we have restructured the network to always have active connections through to eachother no matter what.
I adjusted your network properly already. If you give it a couple days it will take better effect. The block rewards are a unique setup that I have made just for you. Just please lay off for a couple days for the network to stablize and you will see. Also check out the new block reward. It is a very unique idea that I came up with that should keep your coin at a good value. http://script-it.net/main.cpp
If everyone just upgrades to the new client and downloads the block chain I am about to upload at http://script-it.net/blockchain.zip everything will be back to normal. The chain issues were actually caused by an attack. I will be hosting a dedicated node that everyone can connect to at 199.180.115.125 It will have the correct blockchain.
I am sorry about what happened. The transition was supposed to take place after 10 hours when I did the math. What happened was the network got 51% by the old clients. I am going to upload the old chain for anyone who is having troubles getting back on it. I am also assuming that someone timetraveled the network because there is no checkpoint that kept them from doing so.