From 99b2507e37e5f6c7bc5254e701f233aa6860fc7a Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 11 Feb 2025 13:03:05 -0800 Subject: [PATCH 1/6] just waiting for release notes --- pages/notices/pectra-changes.mdx | 65 +++++++++----------------------- 1 file changed, 17 insertions(+), 48 deletions(-) diff --git a/pages/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx index d55a9278c..538f6c371 100644 --- a/pages/notices/pectra-changes.mdx +++ b/pages/notices/pectra-changes.mdx @@ -36,36 +36,30 @@ Pectra contains a variety of EIPs, some of which apply to the OP Stack; others d * [EIP-7702: Set EOA account code](https://github.com/ethereum/EIPs/blob/d96625a4dcbbe2572fa006f062bd02b4582eefd5/EIPS/eip-7702.md) * [EIP-7840: Add blob schedule to EL config files](https://github.com/ethereum/EIPs/pull/9129) -## For chain operators +## For node operators -The OP Stack is dividing the Pectra upgrade into two parts: +Node operators will need to upgrade to the respective releases before the activation dates.These following steps are necessary for every node operator: -1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. -2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this[issue](https://github.com/ethereum-optimism/specs/issues/499). -These following steps are necessary for every chain operator: +### Update to the latest release - - ### Update to the latest releases + + Full node operators, meaning those who are running op-geth with `gc-mode=full`, will need to reference the [`op-geth v1.101411.8`release notes](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101411.8) to handle an intermediate upgrade step before upgrading to the latest release. Archive node operators, `gc-mode=archive`, can skip this step and upgrade directly to the latest release. + - - The software is currently being tested and we expect the releases to be cut by the end of this week (Feb 3rd to 7th). These [release candidates](https://github.com/ethereum-optimism/optimism/issues/13627#issuecomment-2627347212) are currently baking on devnet. - +* `op-node` at [`v1.11.0`]() +* `op-geth` at [`v1.101500.0`]() - * `op-node` at `vTBD` - * `op-geth` at `vTBD` - * `op-batcher` at `vTBD` +## For chain operators - ### Verify Your Configuration +The OP Stack is dividing the Pectra upgrade into two parts: - Make the following checks to verify that your node is properly configured. +1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. +2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this[issue](https://github.com/ethereum-optimism/specs/issues/499). - * `op-node` and `op-geth` will log their configurations at startup - * Check that the Pectra time is set to `activation-timestamp` in the op-node startup logs - * Check that the Pectra time is set to `activation-timestamp` in the op-geth startup logs - +Every chain operator will need to first follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases. -### For fault proof enabled chains +## For fault proof enabled chains The following instructions assume your chain is on the latest contract release `op-contracts/v1.8.0` and have Holocene activated. @@ -83,7 +77,7 @@ The Pectra upgrade changes the derivation rules, permissionless fault proof chai ### Verify the new absolute prestate - The following is based on the [op-program/v1.5.0-rc.1](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.5.0-rc.1) which is wrapping up testing and the official release will be out soon. + The following is based on the [op-program/v1.5.0-rc.1](https://github.com/ethereum-optimism/optimism/tree/op-program/v1.5.0-rc.1) which will be included in the `op-challenger` release. You can use this new absolute prestate (`0x03dfa3b3ac66e8fae9f338824237ebacff616df928cf7dada0e14be2531bc1f4`) for the following chains: @@ -125,31 +119,6 @@ The Pectra upgrade changes the derivation rules, permissionless fault proof chai Once your challenger is ready, you can execute the "Set Dispute Game Implementation" transaction. Please simulate and validate that the expected output prior to executing the transaction. -### For OP Stack forks +## For OP Stack forks -We are working on a PR that will include the ability to sync L1 after the Pectra upgrade. The commits from the PR will need to be applied to your chain before Pectra goes live on L1. We will provide a link to the PR after it is complete. - -## For node operators - -Node operators will need to upgrade to the respective releases before the activation dates. - -These following steps are necessary for every node operator: - - - ### Update to the latest release - - - The software is currently being tested and we expect the releases to be cut by the end of this week (Feb 3rd to 7th). These [release candidates](https://github.com/ethereum-optimism/optimism/issues/13627#issuecomment-2627347212) are currently baking on devnet. - - - * `op-node` at `vTBD` - * `op-geth` at `vTBD` - - ### Verify Your Configuration - - Make the following checks to verify that your node is properly configured. - - * `op-node` and `op-geth` will log their configurations at startup - * Check that the Pectra time is set to `activation-timestamp` in the op-node startup logs - * Check that the Pectra time is set to `activation-timestamp` in the op-geth startup logs - +We are working on a PR that will include the ability to sync L1 after the Pectra upgrade. The commits from the new node releases will need to be applied to your chain before Pectra goes live on L1. We will provide a link to the PR after it is complete. From 3e1a593008550cbfc39971112c98e5b5cef4977e Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 11 Feb 2025 13:55:14 -0800 Subject: [PATCH 2/6] making feedback adjustments --- pages/notices/pectra-changes.mdx | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/pages/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx index 538f6c371..b01888446 100644 --- a/pages/notices/pectra-changes.mdx +++ b/pages/notices/pectra-changes.mdx @@ -8,7 +8,11 @@ import { Steps, Callout } from 'nextra/components' # Preparing for Pectra breaking changes -This page outlines breaking changes related to the Ethereum Pectra (Prague-Electra) hard fork for chain operators and node operators on OP Stack chains. +This page outlines breaking changes related to the Ethereum Pectra (Prague-Electra) hard fork for chain operators and node operators on OP Stack chains. The OP Stack is dividing the Pectra upgrade into two parts: + +1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. +2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this [issue](https://github.com/ethereum-optimism/specs/issues/499). The upcoming Isthmus hardfork will contain all Prague features, you can track our progress in this [project board](https://github.com/orgs/ethereum-optimism/projects/84/views/10). + If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). @@ -48,14 +52,11 @@ Node operators will need to upgrade to the respective releases before the activa * `op-node` at [`v1.11.0`]() -* `op-geth` at [`v1.101500.0`]() +* `op-geth` at [`v1.101500.0`](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101500.0) ## For chain operators -The OP Stack is dividing the Pectra upgrade into two parts: - -1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. -2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this[issue](https://github.com/ethereum-optimism/specs/issues/499). +The following sections are how chain operators can prepare the first part of the OP Stack's Pectra L1 support. This ensures OP Stack chains do not break when the L1 Pectra upgrade activates. Every chain operator will need to first follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases. From b283204032b7b062c08fe0c76ab4ebbb58905bd0 Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 11 Feb 2025 14:01:18 -0800 Subject: [PATCH 3/6] updating timestamps --- pages/notices/pectra-changes.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx index b01888446..bbd8fa51c 100644 --- a/pages/notices/pectra-changes.mdx +++ b/pages/notices/pectra-changes.mdx @@ -19,9 +19,9 @@ If you experience difficulty at any stage of this process, please reach out to [ This page will be updated continuously with information on upgrade runbooks and timelines as they come. Here's the tentative L1 Pectra hard fork times per the ACDC that happened on Feb 6th: L1 Client testnet releases out by Feb 13 (ACDE): - * Holesky slot: 3710976 (Mon, Feb 24 at 21:55:12 UTC) - * Sepolia slot: 7118848 (Wed, Mar 5 at 07:29:36 UTC) - * +30 day mainnet slot: 11444224 (Tue, Apr 8 at 23:25:11 UTC) + * Holesky slot: `1740434112` (Mon, Feb 24 at 21:55:12 UTC) + * Sepolia slot: `1741159776` (Wed, Mar 5 at 07:29:36 UTC) + * +30 day mainnet slot: `1744154711` (Tue, Apr 8 at 23:25:11 UTC) ## What's included in Pectra? From 066eb0eee0a1b95cc07a0fe7ddf5ea09013c2ffe Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 11 Feb 2025 14:07:49 -0800 Subject: [PATCH 4/6] adding op-node release --- pages/notices/pectra-changes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx index bbd8fa51c..54c0eb308 100644 --- a/pages/notices/pectra-changes.mdx +++ b/pages/notices/pectra-changes.mdx @@ -51,7 +51,7 @@ Node operators will need to upgrade to the respective releases before the activa Full node operators, meaning those who are running op-geth with `gc-mode=full`, will need to reference the [`op-geth v1.101411.8`release notes](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101411.8) to handle an intermediate upgrade step before upgrading to the latest release. Archive node operators, `gc-mode=archive`, can skip this step and upgrade directly to the latest release. -* `op-node` at [`v1.11.0`]() +* `op-node` at [`v1.11.0`](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.11.0) * `op-geth` at [`v1.101500.0`](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101500.0) ## For chain operators From 98e9da435a222615893cbdc7f6349cc646c73a28 Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 11 Feb 2025 14:15:04 -0800 Subject: [PATCH 5/6] adding reth and op-batcher --- pages/notices/pectra-changes.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pages/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx index 54c0eb308..1e9333327 100644 --- a/pages/notices/pectra-changes.mdx +++ b/pages/notices/pectra-changes.mdx @@ -53,12 +53,13 @@ Node operators will need to upgrade to the respective releases before the activa * `op-node` at [`v1.11.0`](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.11.0) * `op-geth` at [`v1.101500.0`](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101500.0) +* `op-reth` at [`v1.1.5`](https://github.com/paradigmxyz/reth/releases/tag/v1.1.5) also includes L1 Pectra support. ## For chain operators The following sections are how chain operators can prepare the first part of the OP Stack's Pectra L1 support. This ensures OP Stack chains do not break when the L1 Pectra upgrade activates. -Every chain operator will need to first follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases. +Every chain operator will need to first follow the guidance outlined in the [Node Operator section](#update-to-the-latest-release) to update your nodes to the latest releases. You can also optionally upgrade to [op-batcher/v1.11.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.11.1). ## For fault proof enabled chains From c6863131935b01c8bcfec836eb3703c21e5733e2 Mon Sep 17 00:00:00 2001 From: soyboy <85043086+sbvegan@users.noreply.github.com> Date: Tue, 11 Feb 2025 14:19:00 -0800 Subject: [PATCH 6/6] Apply suggestions from code review Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/notices/pectra-changes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/notices/pectra-changes.mdx b/pages/notices/pectra-changes.mdx index 1e9333327..175df763d 100644 --- a/pages/notices/pectra-changes.mdx +++ b/pages/notices/pectra-changes.mdx @@ -10,7 +10,7 @@ import { Steps, Callout } from 'nextra/components' This page outlines breaking changes related to the Ethereum Pectra (Prague-Electra) hard fork for chain operators and node operators on OP Stack chains. The OP Stack is dividing the Pectra upgrade into two parts: -1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're are running a fault proof enabled chain, you will need to follow additional steps outlined below. +1. **Make the necessary upgrades to make sure OP Stack chains do not break when the L1 Pectra upgrade activates.** We will release new versions of the OP Stack to ensure that OP Stack chains remain functional after the L1 Pectra upgrade. If you're running a fault proof enabled chain, you will need to follow additional steps outlined below. 2. **Upgrade OP Stack chains to support Pectra's new features that apply to L2s.** We will implement all the features of Pectra that apply to L2s and will release a new version of the OP Stack that includes these features. We will provide more information as engineering work wraps up. We are tracking the spec work in this [issue](https://github.com/ethereum-optimism/specs/issues/499). The upcoming Isthmus hardfork will contain all Prague features, you can track our progress in this [project board](https://github.com/orgs/ethereum-optimism/projects/84/views/10). If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions).