The EOS.IO software defines the following process, through which the protocol defined by the specification source code and its composition can be updated:
The block producer proposes to amend the constitution and obtain 15/21 approval.
Block producers maintain 15/21 approval of the new constitution for 30 consecutive days.
All users must use the new constitution as a condition for future transaction processing.
Block producers modify the source code to reflect the changes in the constitution and submit it to the blockchain using the hash of the new constitution.
Block producers maintain 15/21 approval of the new constitution for 30 consecutive days.
The changes to the code will take effect after 7 days. After the source code is approved, all non-production full nodes will have 1 week to upgrade.
All nodes that have not been upgraded to the new code will automatically shut down.
By default, the configuration of the EOS.IO software and the process of updating the blockchain to add new features will take 2 to 3 months, while the update to fix non-critical vulnerabilities that do not require structural changes may require 1 to 2 Time of month.
7.4.1 Urgent changes
If software changes are needed to fix bad or user-damaging security vulnerabilities, block producers may speed up this process. In general, it may violate the Constitution by introducing new features or fixing harmless vulnerabilities to speed up the upgrade.