Update FLIP 204 (#218)

Add more detailed deployment plan, based on timing of Mainnet24 spork. Add link to GitHub epic.
onflow · Nov 7, 2023 · d7d691b · d7d691b
1 parent 592aa7e
commit d7d691b
Showing 1 changed file with 9 additions and 15 deletions.
diff --git a/protocol/20231003-service-account-specified-epoch-switchover.md.md b/protocol/20231003-service-account-specified-epoch-switchover.md.md
@@ -131,6 +131,7 @@ pub fun getTargetEndTimeForEpoch(
 
 
 ### Implementation Plan
+See also [ZenHub epic](https://github.com/onflow/flow-go/issues/4948).
 
 #### Smart Contract
 
@@ -162,21 +163,14 @@ pub fun getTargetEndTimeForEpoch(
     - Default value for deploying `FlowEpoch`
 
 ### Deployment Plan
+#### Mainnet24 (Nov 8 2023)
+1. Prepare patch which makes `EpochSetup` parsing forward-compatible (accept events with the extra `TargetEndTime` field, but discard it).
+2. Rolling upgrade **all nodes** to this patch version.
+3. Upgrade `FlowEpoch` contract.
 
-As usual, deploy to Canary → Testnet → Mainnet
-
-1. Upgrade `FlowEpoch`
-
-    <aside>
-    ⚠️ Caution: First, ensure service event conversion logic is tolerant of additional fields (ignores additional fields)
-
-    </aside>
-
-2. Upgrade Consensus Nodes
-
-    *Comment: Since we are modifying the EpochSetup model, this will likely require a spork.*
-
-
+#### Mainnet25 (Q1-Q2 2024)
+- Deploy `flow-go` version implementing FLIP 204.
+- Since we have already upgraded the contract, no backward-compatibility in `flow-go` code is required (besides the patch above, which will remain on the `mainnet24` branch)
 
 ### Drawbacks
 
@@ -239,4 +233,4 @@ In **Option 1.1** and **2**, the timing of a particular epoch transition does no
 
 #### Why do we set `TargetEndTime` rather than `TargetStartTime`?
 
-The time information is specified in the `EpochSetup` event, which occurs partway through the current epoch. If we specified a `TargetStartTime`, then the PID Controller’s Process Variable would have an undefined value for part of the epoch, and the Cruise Control system would be unable to function. On Mainnet, this corresponds to about 90% of the duration of an epoch.
+The time information is specified in the `EpochSetup` event, which occurs partway through the current epoch. If we specified a `TargetStartTime`, then the PID Controller’s Process Variable would have an undefined value for part of the epoch, and the Cruise Control system would be unable to function. On Mainnet, this corresponds to about 90% of the duration of an epoch.