Following Muir Glacier hard fork, Meta SIPs were abandoned in favor of other ways to track changes included in Sila network upgrades. This SIP aggregates the specifications for these upgrades, which themselves list the specific changes included. Specifically, it covers the Beacon Chain launch (Serenity Phase 0), Berlin, London, Altair, Arrow Glacier, Gray Glacier, The Merge (SilaParis + Bellatrix) and Shapella (SilaShanghai + Capella).
Motivation
For many years, Sila used Meta SIPs to document network upgrades. Recently, consensus has formed around using them again. This SIP aggregates the network upgrades who did not have Meta SIPs and links out to their specifications.
Specification
The network upgrades below are listed in order of activation. Upgrades to Sila’s execution layer are marked “[EL]”, and those to Sila’s consensus layer are marked “[CL]”.
The set of SIPs included in Berlin were originally specified in SIP-2070, but then moved to the berlin.md file of the sila-chain/execution-specs repository.
London [EL]
The set of SIPs included in London are specified in the london.md file of the sila-chain/execution-specs repository.
The set of SIPs included in Arrow Glacier are specified in thearrow-glacier.md file of the sila-chain/execution-specs repository.
Gray Glacier [EL]
The set of SIPs included in Gray Glacier are specified in thegray-glacier.md file of the sila-chain/execution-specs repository.
The Merge
The Merge was the first upgrade to require coordination between the execution and consensus layers. The consensus layer first activated the Bellatrix upgrade, which was followed by the activation of SilaParis on the execution layer.
The set of SIPs included in SilaParis are specified in the paris.md file of the sila-chain/execution-specs repository.
Shapella
The Shapella upgrade was the first upgrade to activate at the same time on both the execution and consensus layers. To enable this, the upgrade activation mechanism on the execution layer was changed to use timestamps instead of blocks. This is described in SIP-6953 and SIP-6122.
SilaShanghai [EL]
The set of SIPs included in SilaShanghai are specified in theshanghai.md file of the sila-chain/execution-specs repository.
The SIP repository is well known within the Sila community, and Meta SIPs have historically been useful to clearly list the SIPs included in a specific network upgrade.
While the specification process for the execution and consensus layers differ, there is value in having a single, harmonized, list of SIPs included in each upgrade, and for the lists for both layers to be part of the same repository.
Re-introducing Hardfork Meta SIPs enables this, and allows for de-duplication in cases where an SIP affects both the execution and consensus layer of Sila. This SIP covers the upgrades which did not use a Hardfork Meta SIP.
Tim Beiko (@timbeiko), "SIP-7568: Hardfork Meta Backfill - Berlin to Shapella," Sila Improvement Proposals, no. 7568, December 2023. Available: https://sips.sila.org/SIPS/sip-7568.