So Bitcoin Core is being challenged by Bitcoin XT (see @dallyshalla s thread [here])
The question that is rapidly becoming relevant for the SAFE network is: how do we manage upgrades in the SAFE network? I’m interested in hearing what ideas you guys come up with. I’ll only share some considerations
- the SAFE network is autonomous, and can host its own binaries (old versions, as well as new proposed updates)
- Bitcoin has a global state in the blockchain and can count votes, setting deadlines as “if 75% of nodes by jan 16 have adopted Bitcoin XT, then Bitcoin XT forks by breaking with Bitcoin Core”, effectively forcing the minority out of business.
- The SAFE network does not have a global state, but it has atomically mutable StructuredData objects, that have (for a low number < ~ 100) a majority vote on mutation.
- obviously it is in the interest of any upgrade to be backwards compatible (a couple of versions); otherwise it would never be adopted; but what are strategies for the network to not fork, tear in higher dimensional connection space, form internal regions that absorb or reject information, … but rather smoothly sails into the future ? - oh yes, local behaviour (SAFE) is far richer than global behaviour (Bitcoin)
: Bitcoin fork divides Bitcoin community