[Protocol Versioning] Deployment plan

[AlexHentschel]

Overarching Product Goal

This issue is part of Epic #6999. The overall goal is to evolve Versioning of Execution Stack to use the Dynamic Protocol State, and subsequently employ this versioning information for

1. coordinating EN HCUs (see Flip 298 for more context on product relevance and impact)
2. the ANs to supports script execution across breaking HCU version boundaries (see OKR description for more context on product relevance and impact)

This issue is part of 1.

Detailed Task Description

Investigate tradeoffs, effort and complexity:

• Deploying the new Versioning Mechanism will require a protocol-level update, because we are adding new logic to the protocol state.

• All nodes need to support the new behaviour. It could be a rolling software deployment proceeding as follows:

  • We are using the protocol-upgrade as a gate for nodes to stop participating that haven't been upgraded.
  • After the protocol has passed the gate-view, we can start using the new service events to schedule Execution Stack upgrades

• Depending on the technical complexity of deploying the new Versioning Mechanism via a rolling update, we could consider including this feature as part of the next spork.

  Document findings Execution State Parameters in the Dynamic Protocol State in and make a decission

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.