Since the dev doesn't seem interested in furthering the goals of the coin and its community anymore...
HMC: Do you have any proposal for a fork, or did I misunderstand and you are not actually interested in committing solutions and code yourself?
I would certainly be willing to work on appropriate patches. However, I am not yet anywhere near having such a patch ready.
Although I've done some small experiments with different options, I don't yet have a solid solution (for the difficulty time warp problem) implemented.
As I see it we have four viable options to controlling block frequency:
* Constrain block frequency by timestamp, as proposed by DeepCryptoAnalyst. Pros are simplicity and ease of implementation. Cons are that it weakens the timestamp reliability (as miners then have incentive to use timestamps as far forward as possible) and increases incentive to timejack (as nodes have incentive to lie about their clock) which may cause problems as rational miners try to maximize profit.
* Introduce forced computational complexity scale into map generation, likely by simply requiring many rounds of hashing. Pros are ease of implementation and a side effect of hampering (current generation) bots. Cons are the possibility that map generation could quickly become sufficiently difficult that human players without specialized hardware could be unlikely to be able to generate a map in reasonable time, and might never be able to begin playing a map. (This could be mitigated some by my "N heads" proposal, though.)
* Introduce forced computational complexity scale into frame calculation itself. This could be done by several mechanisms. Pros are a maximum of network security in all cases, and a side effect of hampering (current generation) bots. Cons are complexity and difficulty of correct implementation, and the possibility for an impact on framerate. (Eventually, difficulty could become high enough that human players without specialized hardware would suffer reduced framerates.)
* "Punt" and move to a classic hash-collision based chain with motogame coinbases being generated in something of a transaction overlay, in the style of Huntercoin. Pros are a maximum of network security in all cases, the fact that we already know that it can work well as it is not a new approach, and the ability to allow merged mining with other chains. Cons are that the coin would become no longer only mined through the single motogame work function.
Does anyone see a fifth option?
Would the best course be to continue the current blockchain or to relaunch?
I don't see any good rationale for a relaunch, and historically relaunches have been devastating for alt-coins. The chain appears to have remained secure, despite the potential for abuse, because miners have acted in the best interests of both the coin and their own financial gain. This is akin to calling for Bitcoin to totally relaunch because ghash has 51% now. (I think anyone who proposed this for btc might just be laughed out of the room.)
We would at the very least need to start a new thread to discuss post-original-developer proposals, aye?
Yes, and we may even want to go so far as to re-brand the coin some.
Perhaps the dev wouldn't mind transferring the ownership of the github, official website/domain and such things to a new lead dev if they are indeed done with it? Or am I jumping ahead of events here?
This would be ideal but, since we still don't even have a response from the devs about the situation, it might be a bit soon to be considering.
If they explicitly do not want to either continue development or give up control of the repository than we will be facing a somewhat tricky situation in handling our hard fork, and will almost certainly want to consider "re-branding" to distinguish our patched client from the original.