Dying coins you want revived / Broken chains you want fixed

Hello,

This is an interesting project. I'd imagine "revival" includes rebasing the legacy code against the more current versions of the repository from which they were originally forked and cloned.
When rebasing older coins onto the updated versions of their parent repositories, there are sometimes hard forks in the parent project which are undesirable to introduce into the legacy coin's code.

For example, suppose some "dead coin" actually still has a swarm of 2 or more full nodes and the blockchain has been running "okay" despite the coin being functionally dead for new users -- implying no DNS Seeds or other problems related to pool hopping and the retarget window.

It would be a bad idea to release new wallets which fork the Main chain, since those remaining nodes have been "the most stable" and there aren't any guarantees they would update their wallets during a community takeover.

In thinking about how these revivals would be implemented practically, I figure there needs to be two releases.
The first release would essentially be a new build of the existing code which included a new checkpoint and updated DNS Seed and pnSeed array addresses.

This first release would essentially bootstrap the revival, giving new and existing users a chance to have a wallet linked against the non-vulnerable OpenSSL libraries and would include the ability to find the swarm of the Main chain without resorting to addnode entries in the configuration file.

Then, the second release could address whatever might have been fundamentally flawed in the original code. Suppose there was some problem related to the propensity for the difficulty to be driven sky high and then a miner abandoning the chain until the difficulty falls back to ground level -- well, "fixing" the retarget window and difficulty adjustment could be discussed on the forum and eventually released. At the same time, since there would be renewed interest; the community could go through all of the things like logo contests and updating the in-wallet graphics which would be integrated into the second release.

This gives time for cool things to happen. After the first release, people can get onboard immediately -- new faucets could be put out there and block explorers could be put up by community members who had otherwise abandoned hope. Since the first release shows goodwill, it would promote interest in furthering efforts to remedy the dead coin for the near future. The buzz around logo contests, faucets and other promotions would help create the larger audience needed for the successful second release where hopefully "things will be fundamentally repaired."

There are other things to consider in general for potential third releases, which might bring the old coin's codebase closer in line with the parent repository -- but that is for discussion later in the thread.

Best Regards,
-Chicago