A blog post by Signal messanger developer moxie0 about development problems and possible threats that the Safe Network will also face after launch. Highlights the danger in the “We’ll just change/fix/update/write new code to address that after launch” attitude (e.g. shall we start with 9 decimal place Safecoin now and “simply” upgrade to 28 later when needed).
History is teaching us that we probably won’t be able to make many changes after launch. The problem only gets worse as the Safe Network becomes really popular. Or will it - perhaps there is a non-centralised development governance method(s) that can be established from the start that help mitigate this well established trend?
From the Signal messenger blog post:
We got to the first production version of IP, and have been trying for the past 20 years to switch to a second production version of IP with limited success. We got to HTTP version 1.1 in 1997, and have been stuck there until now. Likewise, SMTP, IRC, DNS, XMPP, are all similarly frozen in time circa the late 1990s. To answer his question, that’s how far the internet got. It got to the late 90s.
That has taken us pretty far, but it’s undeniable that once you federate your protocol, it becomes very difficult to make changes. And right now, at the application level, things that stand still don’t fare very well in a world where the ecosystem is moving.