Hello,

I would like to add a little to this point, but I'd like to remind that I'm a noob here and this is based on my limited understanding.

The idea quoted is indeed great, the execution that's difficult to be done.

The simplest execution today would be to hard-fork every algorithm change, if I understood correctly. Rofo has already listed some arguments against hard-forks, and why he only wants to do the current planned hard-fork as an emergency measure. As far as I understood hard-forks require synchronization of all wallet versions, so all users participating in the coin's community have to have the wallet properly updated. This is not a problem for most enthusiast users or those that follow the community discussions, but not for the public that the coin is trying to achieve: non-enthusiast, non-technical, normal people. If they don't update the wallet for a hard-fork, or even if one of the "services" they use don't update the wallet (merchant, exchange, etc.) there is a real possibility of money loss.

That said, if there is another way to execute it, I think it's worthy of discussion. As a simple attempt: I would suggest that the algo be scriptable, and all wallets have a peer-to-peer way of determining the active script and therefore algo. Also, any person could submit new scripts implementing new algos, and the community would allow the switch to the new script without needing to change the wallet.

How to do this execution is beyond me. Consider for example it can't be a simple "vote", because otherwise SHA-1 farms would pressure the coin to keep the SHA-1 algo.

Anyway, I hope that this might help a little in the advance of the discussion regarding the point quoted in the beginning.

Thank you,

Janito