I believe the primary vulnerability of Bitcoin is a brand new launch messing issues up in a means that it’ll utterly destroy folks’s religion within the protocol.

By this I imply one thing like what occurred in 2013 with the BerkeleyDB to LevelDB replace. That would have ended rather a lot worse.

If for every launch, there’s a 0,1% likelihood of it messing issues up, then given sufficient time some launch WILL finally mess issues up.

I ponder if a safer method could be to first take a look at the brand new releases privately, in some chosen nodes (and miners), which might be constatly speaking with one another. I the software program in incompatible not directly, they will swiftly coordinate to change again to the outdated software program. That is a lot tougher to do when everybody has put in the brand new software program as a result of there isn’t any strategy to talk with all nodes.

(I do know the software program is closely examined in Testnet beforehand, and that could be a good factor, however it’s not sufficient, just like the 2013 state of affairs confirmed)