iSpace is on the right chain. Cryptsy seems to have ignored requests about updating their wallet. They "forwarded the request to their wallet expert" and that was the only reply I ever got.

@BitcoinNational:
what do you mean about 0 connections on a 1.2.0.0 client? With the addnodes from the OP you should have connections.
Regarding Coin Warz and Bitnodes, their clients have probably crashed due to the mentioned issue. It appears some clients have crashed shortly after the fork. Their clients probably did so too, and they haven't started them again.

The takeover was done because the original dev is gone and eventually even deleted the source from github. You can read all of this in the topic linked in the OP.

We are past fork time and it seems that some may have their client crashing after a while. I am looking into it. In the meantime, try to keep your client online as much as possible and make sure you use the addnodes mentioned above. If your client crashes, please let me know. Including details such as what platform you are on and any usefull log / console entries. If you don't have this issue, please feel free to share that as well. :-)

Block generation on the new chain proves to be much more reliable and consistent.

As a final note: Please understand nobody is supporting the 1.1 version anymore.

Right, good question. Sorry for not mentioning in this post - entirely my bad!
The original dev has gone silent for a long time by now. Regardless of multiple requests to participate in the coin's future. Recently, even the original Github source was removed. This was the time I decided to take matters in my/our own hands. Luckily I still had a up-to-date copy of the source and opened a new Github repo. You can find all of this back in the original TGC launch thread I linked above, but I should have mentioned it here as well.

Please be aware of this new thread: https://bitcointalk.org/index.php?topic=1182854.0

And upgrade your client NOW! Because the fork will be within 24 hours from now!

Hi Tom,

Add the following line to your config file and you should be OK.

Thank you crunck. Much appreciated.

I have released a new version of the Tigercoin client (1.2.0.0) today on github.

I got a little carried away, so included in this new version is:
- a brand new difficulty algo (MultiTermCeiling)
- clients will disconnect anyone with a clock offset > 2 minutes from its own local clock
- a stricter block time algorithm. Max block time is adjusted clock + 4 mnutes (twice the max allowed peer offset)
- support for newer openssl versions
- a new recent chain checkpoint
- a new (an actually valid one this time...) testnet genesis block is included
- new alert keys so we can't get surprised by the former dev

The new difficulty algorithm is designed to be able to handle larger hash power changes on the network. This will result in more stable block generation. To be able to support this new algorithm, you need this new client version.

This update will result in a hard fork of the network. This will happen on Sept 18 (two weeks from now) So make sure you update your client as soon as you read this. I realize this is rather soon, but given the current state of the network I dont expect anyone to have a problem with this.

The more restrictive timer functions will help stabilizing block generation because it will prevent tampering with the network difficulty.

Please check https://bitnodes.net/node/194-135-91-150/ to see how many nodes are running the new version already.

Windows binary is available here: https://mega.nz/#!541GhJoJ!1SQyvCw5oFPIlOsKOlb80NonmC5_5nfMsyovOrVFuj8

And, of coarse, check Github for the source: https://github.com/TigerCoinDev/Tigercoin

Any feedback will be much appreciated.

I just wanted to let you know I am still here. I have been successful with implementing DGW3 and have done some testing on Linux based nodes. At this moment I am working on porting this to Windows binaries and testing it cross platform to make sure I can deliver an easy way to update to the new client for every user and platform.

Please consider this a heads-up for a new upcoming client, and make sure you are following this thread or the new github repository in order to not get left behind. I realise the new Github repo is still a bit fresh, but that will get better soon.

Also, I added a recent checkpoint on Github a few days back. You can check the hash in there using the new block explorer. Thanks marcetin!

Yes, we need a more stable difficulty calculation. I agree. A DGW3 implementation sounds good to me. It is a proven method and easy to implement. I will focus on that for now.

OK let's take matters in our own hands.

I cloned the original Tigercoin code to a new repository:
https://github.com/TigerCoinDev/Tigercoin

Please let me know in case there are any problems with this repo.

This code should be exactly identical to the repository that has recently been removed from Github. I encourage you to check this with any local copies you still have to make sure.