🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 WORK IN PROGRESS 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧

Table of Contents


Scope of this document

In the dedicated sub-protocol working group meeting from April 5th, we concluded that it would be useful to sketch out a possible update process for two exemplary scenarios.

See  👉 Protocol Version Upgrade Mechanisms Discussion (flow forum post) 👈 for terminology


[Scenario 1] Change in block Header

Context

Possible approaches

(A) QC/TC communication

We could expand how we communicate QCs. Though, there would probably be a broad range of affected code. Generally, we want to guarantee that nodes see a QC or TC ending view v-1 (last view of the old protocol version). This must be solved for nodes actively participating as well as nodes catching up. There are a variety of affected implementation areas: