Overall Update Procedure should be smoother

[siebeneicher]

Wheneve a new version of community node goes out, there is a time of transition during which old and new versions exists in parallel. Some community nodes might take days to update.

During transition time:

• transactions should continue to be passed through blocks (by team nodes?)
• 51% attacks should not be possible
• best: automated updates through docker

[alex031029]

Yep.
In the current implementation, team nodes will fill up all proposers committee members if no community nodes are available, to assure the throughput of the chain. The chain will reject all campaign claimed by old version nodes.

Automated updates are truly the best choice. But it still requires you reboot the node. To be honest, a seamless update without reboot is pretty hard to implement.