Will there be a regular hard fork to add features and requirements?

[DavidMc0]

I have very little knowledge on this, but I don’t think a hard fork would be possible in the same way as it is with a blockchain.

If anyone decided to run incompatible software on the main Safe network, they won’t be able to access the data, so it won’t be a useful network except for new data & users who are using their software.

How the network will update to new software is an interesting question, and there are some good threads on updates, though as far as I can see there’s no specific outline of how this will work yet:

How do you update an autonomous network?

Full disclosure: I’m an amateur programmer at best. Launch happens, everything is good then x amount of time goes by and a critical bug is discovered. All of the ‘seed’ servers have been switched off, the network is functioning as its own autonomous collection of nodes - how do you continue to develop a core network under those conditions? What do you use to patch that network? My brain just can’t figure out how something that is actively developed can also be autonomous. I also can’t figure…

Some random thoughts on updating autonomous networks

From what I understand updates to the core code require that the a developer fulfils the predetermined requirements for increased efficiency in the 'autonomous network’, else the changes will be rejected. Any other (perhaps more fundamental) changes to the core code should (in theory from my understanding) be impossible, or else the network would be open to risk of subversion by bad actors. It seems that there are however things which which would, in ultimate terms, improve the efficiency/succe…

Having periodic updates will I’m sure be necessary to keep improving the capabilities of the network, and I’ll be very interested to hear how this process will work.