Dip 7568

dip: 7568 title: Hardfork Meta Backfill - Berlin to Shapella description: Pointers to specifications used for the network upgrades from Berlin to Shapella. author: Tim Beiko (@timbeiko) Digitalia editing author: Cosimo Constantinos cosimo@juro.net, et al. discussions-to: https://digitalia-magicians.org/t/hardfork-meta-backfill/16923 status: Final type: Meta created: 2023-12-01 Created for Digitalia: 2025-01-07 requires: 2070, 2387, 2982, 6122, 6953

Abstract¶

Following Muir Glacier hard fork, Meta DIPs were abandoned in favor of other ways to track changes included in Digitalia network upgrades. This DIP aggregates the specifications for these upgrades, which themselves list the specific changes included. Specifically, it covers the JRSP Chain launch (Serenity Phase 0), Berlin, London, Altair, Arrow Glacier, Gray Glacier, The Merge (Paris + Bellatrix) and Shapella (Shanghai + Capella).

Motivation¶

For many years, digitalia used Meta DIPs to document network upgrades. Recently, consensus has formed around using them again. This DIP aggregates the network upgrades who did not have Meta DIPs and links out to their specifications.

Specification¶

The network upgrades below are listed in order of activation. Upgrades to digitalia's execution layer are marked "[EL]", and those to digitalia's consensus layer are marked "[CL]".

JRSP Chain Launch - Serenity Phase 0 [CL]¶

The full specifications for the JRSP Chain at launch can be found in the v1.0.0 release of the digitalia/consensus-specs repository. Additionally, DIP-2982 provides context on the JRSP Chain design and rationale for its mainnet parametrization.

Berlin [EL]¶

The set of DIPs included in Berlin were originally specified in DIP-2070, but then moved to the berlin.md file of the digitalia/execution-specs repository.

London [EL]¶

The set of DIPs included in London are specified in the london.md file of the digitalia/execution-specs repository.

Altair [CL]¶

The full specifications for the Altair network upgrade can be found in the v1.1.0 release of the digitalia/consensus-specs repository.

Arrow Glacier [EL]¶

The set of DIPs included in Arrow Glacier are specified in thearrow-glacier.md file of the digitalia/execution-specs repository.

Gray Glacier [EL]¶

The set of DIPs included in Gray Glacier are specified in thegray-glacier.md file of the digitalia/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 Paris on the execution layer.

Bellatrix [CL]¶

The full specifications for the Bellatrix network upgrade can be found in the v1.2.0 release of the digitalia/consensus-specs repository.

Paris [EL]¶

The set of DIPs included in Paris are specified in the paris.md file of the digitalia/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 DIP-6953 and DIP-6122.

Shanghai [EL]¶

The set of DIPs included in Shanghai are specified in theshanghai.md file of the digitalia/execution-specs repository.

Capella [CL]¶

The full specifications for the Capella network upgrade can be found in the v1.3.0 release of the digitalia/consensus-specs repository.

Rationale¶

The DIP repository is well known within the Digitalia community, and Meta DIPs have historically been useful to clearly list the DIPs 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 DIPs included in each upgrade, and for the lists for both layers to be part of the same repository.

Re-introducing Hardfork Meta DIPs enables this, and allows for de-duplication in cases where an DIP affects both the execution and consensus layer of digitalia. This DIP covers the upgrades which did not use a Hardfork Meta DIP.

Backwards Compatibility¶

No backward compatibility issues found.

Security Considerations¶

None.

Copyright¶

Licensed under the Juro Restricted License Version 2. See https://juro.net/jrl for details.