From ab13d2bac36f66fca5b50414276e5f95696d1ebc Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 09:49:57 -0800 Subject: [PATCH 01/15] WIP Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-meta-hardfork-meta.md | 127 +++++++++++++++++++++++++++++++++ 1 file changed, 127 insertions(+) create mode 100644 EIPS/eip-meta-hardfork-meta.md diff --git a/EIPS/eip-meta-hardfork-meta.md b/EIPS/eip-meta-hardfork-meta.md new file mode 100644 index 00000000000000..998d89bc001b6e --- /dev/null +++ b/EIPS/eip-meta-hardfork-meta.md @@ -0,0 +1,127 @@ +--- +title: Meta Hardfork Meta, from Berlin to Shapella +description: Pointers to specifications used for the network upgrades from Berlin to Shapella. +author: Tim Beiko (@timbeiko) +discussions-to: TBA +status: Draft +type: Meta +created: 2023-12-01 +requires: 2070, 2982 +--- + +## Abstract + +Between the Berlin and Shapella network upgrades, Meta EIPs were abandoned in favor of other ways of tracking changes made as part of Ethereum network upgrades. This EIP links the canonical specification used for each of these forks, to provide a complete reference. + +## Motivation + +For many years, Ethereum used Meta EIPs to document network upgrades. Recently, consensus has formed around using them again. This EIP acts as a backfill, linking out the specifications for upgrades which did not have Meta EIPs. + +## Specification + +The network upgrades below are listed in order of activation on the Ethereum network. Upgrades to Ethereum's execution layer are marked [EL], and those to Ethereum's consensus layer are marked [CL]. + +### Beacon Chain Launch - Serenity Phase 0 [CL] + +The full specifications for the Beacon Chain at launch can be found in the [v.1.0.0 release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/579da6d2dc734b269dbf67aa1004b54bb9449784). Additionally, [EIP-2982](./eip-2982.md) provides context on the overall Beacon Chain design and rationale for the parameterization. + +### Berlin [EL] + +The Berlin upgrade was originally specified in [EIP-2070](./eip-2079.md), but was then moved to the [`berlin.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/berlin.md) file of the `ethereum/execution-specs` repository. + +### London [EL] + +The original London upgrade specifications can be found in the [`london.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/london.md) file of the `ethereum/execution-specs` repository. + +### Altair [CL] + +### Arrow Glacier [EL] + +The original Arrow Glacier upgrade specifications can be found in the [`arrow-glacier.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/arrow-glacier.md) file of the `ethereum/execution-specs` repository. + +### Gray Glacier [EL] + +The original Gray Glacier upgrade specifications can be found in the [`gray-glacier.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/gray-glacier.md) file of the `ethereum/execution-specs` repository. + +### The Merge + +#### Bellatrix [CL] + +#### Paris [EL] + +The original Paris upgrade specifications can be found in the [`paris.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/paris.md) file of the `ethereum/execution-specs` repository. + + +### Shapella + +#### Shanghai [EL] + +The original Shanghai upgrade specifications can be found in the [`shanghai.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/shanghai.md) file of the `ethereum/execution-specs` repository. + +#### Capella [CL] + + +## Rationale + + + +TBD + +## Backwards Compatibility + + + +No backward compatibility issues found. + +## Test Cases + + + +## Reference Implementation + + + +## Security Considerations + + + +Needs discussion. + +## Copyright + +Copyright and related rights waived via [CC0](../LICENSE.md). From 4d0239dea49bead4932510ef6dab7b669107512f Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 11:45:53 -0800 Subject: [PATCH 02/15] meta meta draft Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-meta-hardfork-meta.md | 88 ++++++++++------------------------ 1 file changed, 26 insertions(+), 62 deletions(-) diff --git a/EIPS/eip-meta-hardfork-meta.md b/EIPS/eip-meta-hardfork-meta.md index 998d89bc001b6e..9386e587845a5e 100644 --- a/EIPS/eip-meta-hardfork-meta.md +++ b/EIPS/eip-meta-hardfork-meta.md @@ -1,126 +1,90 @@ --- -title: Meta Hardfork Meta, from Berlin to Shapella +title: Hardfork Meta Backfill, from Berlin to Shapella description: Pointers to specifications used for the network upgrades from Berlin to Shapella. author: Tim Beiko (@timbeiko) discussions-to: TBA status: Draft type: Meta created: 2023-12-01 -requires: 2070, 2982 +requires: 2070, 2982, 6122, 6953 --- ## Abstract -Between the Berlin and Shapella network upgrades, Meta EIPs were abandoned in favor of other ways of tracking changes made as part of Ethereum network upgrades. This EIP links the canonical specification used for each of these forks, to provide a complete reference. +Between the Berlin and Shapella hard forks, Meta EIPs were abandoned in favor of other ways to track changes included in Ethereum network upgrades. This EIP aggregates the specifications for these upgrades. Specifically, it covers the Beacon Chain launch (Serenity Phase 0), Berlin, London, Altair, Arrow Glacier, Gray Glacier, The Merge (Paris + Bellatrix) and Shapella (Shanghai + Capella). ## Motivation -For many years, Ethereum used Meta EIPs to document network upgrades. Recently, consensus has formed around using them again. This EIP acts as a backfill, linking out the specifications for upgrades which did not have Meta EIPs. +For many years, Ethereum used Meta EIPs to document network upgrades. Recently, consensus has formed around using them again. This EIP aggregates the network upgrades who did not have Meta EIPs and links out to their specifications. ## Specification -The network upgrades below are listed in order of activation on the Ethereum network. Upgrades to Ethereum's execution layer are marked [EL], and those to Ethereum's consensus layer are marked [CL]. +The network upgrades below are listed in order of activation. Upgrades to Ethereum's execution layer are marked "[EL]", and those to Ethereum's consensus layer are marked "[CL]". ### Beacon Chain Launch - Serenity Phase 0 [CL] -The full specifications for the Beacon Chain at launch can be found in the [v.1.0.0 release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/579da6d2dc734b269dbf67aa1004b54bb9449784). Additionally, [EIP-2982](./eip-2982.md) provides context on the overall Beacon Chain design and rationale for the parameterization. +The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.0.0). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parameterization. ### Berlin [EL] -The Berlin upgrade was originally specified in [EIP-2070](./eip-2079.md), but was then moved to the [`berlin.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/berlin.md) file of the `ethereum/execution-specs` repository. +The set of EIPs included in Berlin were originally specified in [EIP-2070](./eip-2079.md), but then moved to the [`berlin.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/berlin.md) file of the `ethereum/execution-specs` repository. ### London [EL] -The original London upgrade specifications can be found in the [`london.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/london.md) file of the `ethereum/execution-specs` repository. +The set of EIPs included in London are specified in the [`london.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/london.md) file of the `ethereum/execution-specs` repository. ### Altair [CL] +The full specfications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.1.0). + ### Arrow Glacier [EL] -The original Arrow Glacier upgrade specifications can be found in the [`arrow-glacier.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/arrow-glacier.md) file of the `ethereum/execution-specs` repository. +The set of EIPs included in Arrow Glacier are specified in the[`arrow-glacier.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/arrow-glacier.md) file of the `ethereum/execution-specs` repository. ### Gray Glacier [EL] -The original Gray Glacier upgrade specifications can be found in the [`gray-glacier.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/gray-glacier.md) file of the `ethereum/execution-specs` repository. +The set of EIPs included in Gray Glacier are specified in the[`gray-glacier.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/gray-glacier.md) file of the `ethereum/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] -#### Paris [EL] +The full specfications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.2.0). -The original Paris upgrade specifications can be found in the [`paris.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/paris.md) file of the `ethereum/execution-specs` repository. +#### Paris [EL] +The set of EIPs included in Paris are specified in the [`paris.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/paris.md) file of the `ethereum/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 [EIP-6953](./6953) and [EIP-6122](./6122). + #### Shanghai [EL] -The original Shanghai upgrade specifications can be found in the [`shanghai.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/shanghai.md) file of the `ethereum/execution-specs` repository. +The set of EIPs included in Shanghai are specified in the[`shanghai.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/shanghai.md) file of the `ethereum/execution-specs` repository. #### Capella [CL] +The full specfications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.3.0). -## Rationale - +While the specification process for the execution and consensus layers differ, there is value in having a single, harmonized, list of EIPs included in each upgrade, and for the lists for both layers to be part of the same repository. -TBD +Re-introducing Hardfork Meta EIPs enables this, and allows for deduplication in cases where an EIP affects both the execution and consensus layer of Ethereum. This EIP covers the upgrades which did not use a Hardfork Meta EIP. ## Backwards Compatibility - - No backward compatibility issues found. -## Test Cases - - - -## Reference Implementation - - - ## Security Considerations - - -Needs discussion. +None. ## Copyright From 86355d741344010ec051605e310f14fe9637d87f Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 11:51:05 -0800 Subject: [PATCH 03/15] typos + EthMag Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-meta-hardfork-meta.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/EIPS/eip-meta-hardfork-meta.md b/EIPS/eip-meta-hardfork-meta.md index 9386e587845a5e..a34b296c17c573 100644 --- a/EIPS/eip-meta-hardfork-meta.md +++ b/EIPS/eip-meta-hardfork-meta.md @@ -2,7 +2,7 @@ title: Hardfork Meta Backfill, from Berlin to Shapella description: Pointers to specifications used for the network upgrades from Berlin to Shapella. author: Tim Beiko (@timbeiko) -discussions-to: TBA +discussions-to: https://ethereum-magicians.org/t/hardfork-meta-backfill/1692 status: Draft type: Meta created: 2023-12-01 @@ -23,7 +23,7 @@ The network upgrades below are listed in order of activation. Upgrades to Ethere ### Beacon Chain Launch - Serenity Phase 0 [CL] -The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.0.0). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parameterization. +The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.0.0). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parametrization. ### Berlin [EL] @@ -35,7 +35,7 @@ The set of EIPs included in London are specified in the [`london.md`](https://gi ### Altair [CL] -The full specfications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.1.0). +The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.1.0). ### Arrow Glacier [EL] @@ -51,7 +51,7 @@ The Merge was the first upgrade to require coordination between the execution an #### Bellatrix [CL] -The full specfications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.2.0). +The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.2.0). #### Paris [EL] @@ -67,7 +67,7 @@ The set of EIPs included in Shanghai are specified in the[`shanghai.md`](https:/ #### Capella [CL] -The full specfications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.3.0). +The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.3.0). ## Rationale @@ -76,7 +76,7 @@ The EIP repository is well known within the Ethereum community, and Meta EIPs ha While the specification process for the execution and consensus layers differ, there is value in having a single, harmonized, list of EIPs included in each upgrade, and for the lists for both layers to be part of the same repository. -Re-introducing Hardfork Meta EIPs enables this, and allows for deduplication in cases where an EIP affects both the execution and consensus layer of Ethereum. This EIP covers the upgrades which did not use a Hardfork Meta EIP. +Re-introducing Hardfork Meta EIPs enables this, and allows for de-duplication in cases where an EIP affects both the execution and consensus layer of Ethereum. This EIP covers the upgrades which did not use a Hardfork Meta EIP. ## Backwards Compatibility From 47c5480717e95f47c4b95751ce20e2042e630ed0 Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 12:14:55 -0800 Subject: [PATCH 04/15] fix links Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-meta-hardfork-meta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-meta-hardfork-meta.md b/EIPS/eip-meta-hardfork-meta.md index a34b296c17c573..35e2b127b96fda 100644 --- a/EIPS/eip-meta-hardfork-meta.md +++ b/EIPS/eip-meta-hardfork-meta.md @@ -59,7 +59,7 @@ The set of EIPs included in Paris are specified in the [`paris.md`](https://gith ### 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 [EIP-6953](./6953) and [EIP-6122](./6122). +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 [EIP-6953](./eip-6953) and [EIP-6122](./eip-6122). #### Shanghai [EL] From 316e7cfa1af45f2bde843f1ab5db43da96ae20c6 Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:13:28 -0800 Subject: [PATCH 05/15] fix typo Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/{eip-meta-hardfork-meta.md => eip-7568.md} | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) rename EIPS/{eip-meta-hardfork-meta.md => eip-7568.md} (98%) diff --git a/EIPS/eip-meta-hardfork-meta.md b/EIPS/eip-7568.md similarity index 98% rename from EIPS/eip-meta-hardfork-meta.md rename to EIPS/eip-7568.md index 35e2b127b96fda..6a77c085d2e2c3 100644 --- a/EIPS/eip-meta-hardfork-meta.md +++ b/EIPS/eip-7568.md @@ -1,4 +1,5 @@ --- +eip: 7568 title: Hardfork Meta Backfill, from Berlin to Shapella description: Pointers to specifications used for the network upgrades from Berlin to Shapella. author: Tim Beiko (@timbeiko) @@ -27,7 +28,7 @@ The full specifications for the Beacon Chain at launch can be found in the [`v1. ### Berlin [EL] -The set of EIPs included in Berlin were originally specified in [EIP-2070](./eip-2079.md), but then moved to the [`berlin.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/berlin.md) file of the `ethereum/execution-specs` repository. +The set of EIPs included in Berlin were originally specified in [EIP-2070](./eip-2070.md), but then moved to the [`berlin.md`](https://github.com/ethereum/execution-specs/blob/8dbde99b132ff8d8fcc9cfb015a9947ccc8b12d6/network-upgrades/mainnet-upgrades/berlin.md) file of the `ethereum/execution-specs` repository. ### London [EL] From 18a4950e5d93cdad775cbd5ff0ae4d5f938ccb0e Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:14:52 -0800 Subject: [PATCH 06/15] Fix title Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index 6a77c085d2e2c3..e96a103ebbeec5 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -1,6 +1,6 @@ --- eip: 7568 -title: Hardfork Meta Backfill, from Berlin to Shapella +title: Hardfork Meta Backfill - Berlin to Shapella description: Pointers to specifications used for the network upgrades from Berlin to Shapella. author: Tim Beiko (@timbeiko) discussions-to: https://ethereum-magicians.org/t/hardfork-meta-backfill/1692 From a395f491fbaf58277f57af9ea0a0b27129f6a980 Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:16:13 -0800 Subject: [PATCH 07/15] Fix Capella link Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index e96a103ebbeec5..b8e0f72c6128af 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -68,7 +68,7 @@ The set of EIPs included in Shanghai are specified in the[`shanghai.md`](https:/ #### Capella [CL] -The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.3.0). +The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/tree/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa). ## Rationale From b51675ffccd2903599a9f9f45245a1a31a4ae13c Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:17:22 -0800 Subject: [PATCH 08/15] tree -> blob Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index b8e0f72c6128af..2896b07a5e2493 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -68,7 +68,7 @@ The set of EIPs included in Shanghai are specified in the[`shanghai.md`](https:/ #### Capella [CL] -The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/tree/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa). +The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa). ## Rationale From 35b8dce4973f4df802a672dac8b081da131c403b Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:34:29 -0800 Subject: [PATCH 09/15] Use blobs instead of versions for CL Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index 2896b07a5e2493..55583ba35fa28e 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -24,7 +24,7 @@ The network upgrades below are listed in order of activation. Upgrades to Ethere ### Beacon Chain Launch - Serenity Phase 0 [CL] -The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.0.0). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parametrization. +The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/579da6d2dc734b269dbf67aa1004b54bb9449784). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parametrization. ### Berlin [EL] @@ -36,7 +36,7 @@ The set of EIPs included in London are specified in the [`london.md`](https://gi ### Altair [CL] -The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.1.0). +The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/67fd7979ffd705bd6b0b5c1aaa842a445cc74d9a). ### Arrow Glacier [EL] @@ -52,7 +52,7 @@ The Merge was the first upgrade to require coordination between the execution an #### Bellatrix [CL] -The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/v1.2.0). +The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/f8ae982c2fc7dbb03a3c95a638da4486310e09e9). #### Paris [EL] From 070c5c4430b14b61d6bafce84a49181ed4524f13 Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:37:06 -0800 Subject: [PATCH 10/15] Add slashes Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index 55583ba35fa28e..e1a24610cf8f07 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -36,7 +36,7 @@ The set of EIPs included in London are specified in the [`london.md`](https://gi ### Altair [CL] -The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/67fd7979ffd705bd6b0b5c1aaa842a445cc74d9a). +The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/67fd7979ffd705bd6b0b5c1aaa842a445cc74d9a/). ### Arrow Glacier [EL] @@ -52,7 +52,7 @@ The Merge was the first upgrade to require coordination between the execution an #### Bellatrix [CL] -The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/f8ae982c2fc7dbb03a3c95a638da4486310e09e9). +The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/f8ae982c2fc7dbb03a3c95a638da4486310e09e9/). #### Paris [EL] @@ -68,7 +68,7 @@ The set of EIPs included in Shanghai are specified in the[`shanghai.md`](https:/ #### Capella [CL] -The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa). +The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa/). ## Rationale From 148cf12569ac68a15ea7b0af3089cd8d097c32d6 Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:47:56 -0800 Subject: [PATCH 11/15] link readme Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index e1a24610cf8f07..c46e7a821fb1a5 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -68,7 +68,7 @@ The set of EIPs included in Shanghai are specified in the[`shanghai.md`](https:/ #### Capella [CL] -The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa/). +The full specifications for the Capella network upgrade can be found in the [`v1.3.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/01b53691dcc36d37a5ad8994b3a32d8de69fb1aa/README.md#stable-specifications). ## Rationale From 52b65da5fa58197f7c651019a47cef017fea1065 Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Fri, 1 Dec 2023 13:50:15 -0800 Subject: [PATCH 12/15] moar readmes Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index c46e7a821fb1a5..6d2528cbc226ab 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -24,7 +24,7 @@ The network upgrades below are listed in order of activation. Upgrades to Ethere ### Beacon Chain Launch - Serenity Phase 0 [CL] -The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/579da6d2dc734b269dbf67aa1004b54bb9449784). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parametrization. +The full specifications for the Beacon Chain at launch can be found in the [`v1.0.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/579da6d2dc734b269dbf67aa1004b54bb9449784/README.md#phase-0). Additionally, [EIP-2982](./eip-2982.md) provides context on the Beacon Chain design and rationale for its mainnet parametrization. ### Berlin [EL] @@ -36,7 +36,7 @@ The set of EIPs included in London are specified in the [`london.md`](https://gi ### Altair [CL] -The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/67fd7979ffd705bd6b0b5c1aaa842a445cc74d9a/). +The full specifications for the Altair network upgrade can be found in the [`v1.1.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/67fd7979ffd705bd6b0b5c1aaa842a445cc74d9a/README.md#altair). ### Arrow Glacier [EL] @@ -52,7 +52,7 @@ The Merge was the first upgrade to require coordination between the execution an #### Bellatrix [CL] -The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/f8ae982c2fc7dbb03a3c95a638da4486310e09e9/). +The full specifications for the Bellatrix network upgrade can be found in the [`v1.2.0` release of the `ethereum/consensus-specs` repository](https://github.com/ethereum/consensus-specs/blob/f8ae982c2fc7dbb03a3c95a638da4486310e09e9/README.md#stable-specifications). #### Paris [EL] From c34a38c676f2fa6d7c4069668e805fa72dd8eccb Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Sat, 2 Dec 2023 09:25:15 -0800 Subject: [PATCH 13/15] Add .md Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index 6d2528cbc226ab..2c2dfa49e92561 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -60,7 +60,7 @@ The set of EIPs included in Paris are specified in the [`paris.md`](https://gith ### 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 [EIP-6953](./eip-6953) and [EIP-6122](./eip-6122). +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 [EIP-6953](./eip-6953.md) and [EIP-6122](./eip-6122.md). #### Shanghai [EL] From 0862c0d5ddfeffbf580c78e4837a34dae455a93a Mon Sep 17 00:00:00 2001 From: Tim Beiko <9390255+timbeiko@users.noreply.github.com> Date: Thu, 7 Dec 2023 10:24:04 -0800 Subject: [PATCH 14/15] Address comments Signed-off-by: Tim Beiko <9390255+timbeiko@users.noreply.github.com> --- EIPS/eip-7568.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index 2c2dfa49e92561..9744a6d91ad09f 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -3,16 +3,16 @@ eip: 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) -discussions-to: https://ethereum-magicians.org/t/hardfork-meta-backfill/1692 +discussions-to: https://ethereum-magicians.org/t/hardfork-meta-backfill/16923 status: Draft type: Meta created: 2023-12-01 -requires: 2070, 2982, 6122, 6953 +requires: 2070, 2387, 2982, 6122, 6953, --- ## Abstract -Between the Berlin and Shapella hard forks, Meta EIPs were abandoned in favor of other ways to track changes included in Ethereum network upgrades. This EIP aggregates the specifications for these upgrades. Specifically, it covers the Beacon Chain launch (Serenity Phase 0), Berlin, London, Altair, Arrow Glacier, Gray Glacier, The Merge (Paris + Bellatrix) and Shapella (Shanghai + Capella). +Following Muir Glacier hard fork, Meta EIPs were abandoned in favor of other ways to track changes included in Ethereum network upgrades. This EIP 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 (Paris + Bellatrix) and Shapella (Shanghai + Capella). ## Motivation From af1d0d7bd7fcc227f9f09b917cdadcdca232b853 Mon Sep 17 00:00:00 2001 From: lightclient <14004106+lightclient@users.noreply.github.com> Date: Thu, 7 Dec 2023 11:49:19 -0700 Subject: [PATCH 15/15] 7568: fix requires line --- EIPS/eip-7568.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7568.md b/EIPS/eip-7568.md index 9744a6d91ad09f..e58a27a8dc1af3 100644 --- a/EIPS/eip-7568.md +++ b/EIPS/eip-7568.md @@ -7,7 +7,7 @@ discussions-to: https://ethereum-magicians.org/t/hardfork-meta-backfill/16923 status: Draft type: Meta created: 2023-12-01 -requires: 2070, 2387, 2982, 6122, 6953, +requires: 2070, 2387, 2982, 6122, 6953 --- ## Abstract