github onflow/flow-go v0.39.0
Protocol Upgrade - EFM Recovery

latest releases: v0.39.0-cdp-engine, v0.38.4
pre-releaseone day ago

What's Changed

⬆️ Coordinated Upgrades for all Node Roles

This is a mechanism built into the Protocol State which enables view-coordinated upgrades to the Protocol State data model. This mechanism can be leveraged to implement coordinated behavioural changes ("protocol upgrades") for all node roles, including for backward-incompatible upgrades. Previously such upgrades were supported only for Execution Nodes and the Execution stack via the Height Coordinated Upgrade mechanism and VersionBeacon smart contract.

This release completes the upgrade feature and implements the first such coordinated upgrade, which will be used to enable EFM Recovery (see below). Further details are in the working group meeting notes.

Related PRs

🌟 Epoch Fallback Mode Recovery

Epoch Fallback Mode (EFM) is a operational mode triggered when an epoch transition fails for any reason. While in EFM, the current epoch is extended in perpetuity and epoch transitions are disabled. This has the effect of disabling changes to the node operator committee. Also, automatic reward payout is disabled and reverts to a manual governance transaction.

EFM Recovery provides a mechanism to recover from epoch failures using a governance transaction. Previously, recovery from EFM required a network upgrade (spork). With EFM Recovery, a governance transaction is used to resume epoch transitions. Further details are in the design document.

EFM Recovery is available in this release, but must be enabled via a coordinated upgrade (see above).

Related PRs

🪨 Storage Layer

⛰️ Access API

❓ Miscellaneous

Full Changelog: v0.38.3...v0.39.0

Don't miss a new flow-go release

NewReleases is sending notifications on new releases.