You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once the previous issue #7000 is done, we can store the Execution Stack Version (and other protocol parameters controlling the execution) in the Dynamic protocol state. Now we need to add functionality for updating these parameters in the Protocol State:
implement Service Events on the protocol layer only (flow-go) for requesting to schedule a value update
Janez to define the rules by which request for scheduling an update should be accepted or rejected
The text was updated successfully, but these errors were encountered:
AlexHentschel
changed the title
Once the previous issue (☝) is done, we can store the Execution Stack Version (and other protocol parameters controlling the execution) in the Dynamic protocol state. Now we need to add functionality for updating these parameters in the Protocol State:
[Protocol Versioning] functionality for updating execution-related parameters in the Protocol State
Mar 7, 2025
Once the previous issue #7000 is done, we can store the Execution Stack Version (and other protocol parameters controlling the execution) in the Dynamic protocol state. Now we need to add functionality for updating these parameters in the Protocol State:
flow-go
) for requesting to schedule a value updateKeyValueStoreStateMachine
and add this to the Protocol State'sEvolveState
methodThe text was updated successfully, but these errors were encountered: