From 4239878d6555ff12307c481025659e469445e1a9 Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 12 Nov 2024 17:59:31 +0700 Subject: [PATCH 01/12] holocene notice draft --- pages/builders/notices/_meta.json | 1 + pages/builders/notices/holocene-changes.mdx | 77 +++++++++++++++++++++ 2 files changed, 78 insertions(+) create mode 100644 pages/builders/notices/holocene-changes.mdx diff --git a/pages/builders/notices/_meta.json b/pages/builders/notices/_meta.json index f75d9972e..4b21e6372 100644 --- a/pages/builders/notices/_meta.json +++ b/pages/builders/notices/_meta.json @@ -1,3 +1,4 @@ { + "holocene-changes": "Preparing for Holocene breaking changes", "sdk-deprecation": "Preparing for Optimism SDK deprecation" } diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx new file mode 100644 index 000000000..639296f52 --- /dev/null +++ b/pages/builders/notices/holocene-changes.mdx @@ -0,0 +1,77 @@ +--- +title: Preparing for Holocene Breaking Changes +lang: en-US +description: Learn how to prepare for Holocene upgrade breaking changes. +--- + +import { Steps, Callout } from 'nextra/components' + +# Preparing for Holocene breaking changes + +This page outlines breaking changes related to the Holocene network upgrade for chain operators, and node operators. +If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). + + +The Holocene upgrade for the Sepolia Superchain will be activated at **Tue Nov 26 at 15:00:00 UTC (unix timestamp** `1732633200`). + +The Holocene upgrade for the Mainnet Superchain is planned to happen on **Thu 9 Jan 2025 18:00:01 UTC**, [governance proposal link to be added](). + + +## What's Included in Holocene + +Holocene contains two changes: + +- **Holocene block derivation**: a set of changes that render the derivation pipeline stricter and simpler, improving worst-case scenarios for Fault Proofs and Interoperability. +- **EIP-1559 configurability**: The elasticity and denominator EIP-1559 parameters become configurable via the `SystemConfig` L1 contract, allowing the gas target and gas limit to be configured independently. + + For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html). + +## For Chain Operators + +Since the Holocene upgrade changes the execution and derivation rules, all chain and node operators, as for all hardforks, have to upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides, see below. + +Besides this, chain operators must upgrade their chain’s `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1). The updated `SystemConfig` implementations are deployed at addresses + +- Sepolia: TBD +- Mainnet: TBD + +Chain operators need to update their proxy contracts to point to these new implementations. The following upgrade script can be used to facilitate the upgrade: https://github.com/ethereum-optimism/optimism/pull/12878 + + +### For fault proof enabled chains + + + +## For node operators + +Node operators will need to upgrade to a Holocene release before the activation date. For Sepolia, the op-node release [FIND CORRECT VERSION](todo: add link) and op-geth release [FIND CORRECT VERSION](todo: add link) contain these changes. + +These following steps are necessary for every node operator: + + + ### Update to the latest release + + * [`op-geth`](FIND_CORRECT_LINK) + * [`op-node`](FIND_CORRECT_LINK) + + ### Configure the Holocene activation date + + + If you are operating a node for an OP Chain that have opted into the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), the Holocene activation date is part of the `op-node` and `op-geth` nodes. So, no action is needed for the sequencer after upgrading to the latest release. Please skip to [Step 3: Verify Your Configuration](#verify-your-configuration). + + For Sepolia that is: `OP Sepolia`, `Base Sepolia`, `Mode Sepolia`, and `Zora Sepolia`. + + + For node operators of not included in the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), you will need to manually configure the [activation timestamp](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml). This can be done one of two ways: + + * **Option 1:** Set the activation time in the `rollup.json` for `op-node`. You will still need to set the `override.granite` flag in `op-geth` if you use this option. + * **Option 2:** Set the activation time via overrides (CLI) in both `op-node` and `op-geth`. These will need to be set on `op-node` and `op-geth` for the sequencer and all other nodes. + + ### 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 Granite time is set to `activation-timestamp` in the op-node startup logs + * Check that the Granite time is set to `activation-timestamp` in the op-geth startup logs + \ No newline at end of file From 0fb789562069a059414c9e182445160c17d8beff Mon Sep 17 00:00:00 2001 From: soyboy Date: Wed, 13 Nov 2024 16:09:52 +0700 Subject: [PATCH 02/12] adding notice page edits --- pages/builders/notices/holocene-changes.mdx | 27 ++++++++++++++------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index 639296f52..54b2a560b 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -14,23 +14,25 @@ If you experience difficulty at any stage of this process, please reach out to [ The Holocene upgrade for the Sepolia Superchain will be activated at **Tue Nov 26 at 15:00:00 UTC (unix timestamp** `1732633200`). -The Holocene upgrade for the Mainnet Superchain is planned to happen on **Thu 9 Jan 2025 18:00:01 UTC**, [governance proposal link to be added](). +The Holocene upgrade for the Mainnet Superchain is optimistically scheduled for **Thu 9 Jan 2025 18:00:01 UTC**, pending governance approval. -## What's Included in Holocene +## What's included in Holocene Holocene contains two changes: -- **Holocene block derivation**: a set of changes that render the derivation pipeline stricter and simpler, improving worst-case scenarios for Fault Proofs and Interoperability. +- **Holocene block derivation**: a set of changes that render the derivation pipeline stricter and simpler, improving worst-case scenarios for the Fault Proof System and Interoperability. - **EIP-1559 configurability**: The elasticity and denominator EIP-1559 parameters become configurable via the `SystemConfig` L1 contract, allowing the gas target and gas limit to be configured independently. For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html). -## For Chain Operators +## For chain operators -Since the Holocene upgrade changes the execution and derivation rules, all chain and node operators, as for all hardforks, have to upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides, see below. +Chain operators have to upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides. -Besides this, chain operators must upgrade their chain’s `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1). The updated `SystemConfig` implementations are deployed at addresses +TODO: is this a must? for mode, metal, and zora sepolia they're on op-contracts/v1.3.0; but they're also opted into superchain wide upgrades. + +Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1). The updated `SystemConfig` implementations are deployed at addresses - Sepolia: TBD - Mainnet: TBD @@ -40,11 +42,18 @@ Chain operators need to update their proxy contracts to point to these new imple ### For fault proof enabled chains +Since the Holocene upgrade changes the execution and derivation rules, the version of `op-program` used in the fault proof system has to be upgraded to a version that includes the Holocene activation date for the chain. The `op-program` version used is specified via the `faultGameAbsolutePrestate` setting, deployed as part of `FaultDisputeGame` and `PermissionedDisputeGame` contracts. Additionally, the `MIPS` contract must be upgraded to support additional calls made by the new `op-program`. + +The `FaultDisputeGame` and `PermissionedDisputeGame` contracts must be deployed separately for each chain. The `MIPS` contract implementation can be shared by all chains and is deployed at: + +- Sepolia: TBD +- Mainnet: TBD +Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The following upgrade script can be used to facilitate the upgrade: https://github.com/ethereum-optimism/optimism/pull/12878 ## For node operators -Node operators will need to upgrade to a Holocene release before the activation date. For Sepolia, the op-node release [FIND CORRECT VERSION](todo: add link) and op-geth release [FIND CORRECT VERSION](todo: add link) contain these changes. +Node operators will need to upgrade to the respective Holocene releases before the activation dates. These following steps are necessary for every node operator: @@ -62,9 +71,9 @@ These following steps are necessary for every node operator: For Sepolia that is: `OP Sepolia`, `Base Sepolia`, `Mode Sepolia`, and `Zora Sepolia`. - For node operators of not included in the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), you will need to manually configure the [activation timestamp](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml). This can be done one of two ways: + For node operators of not included in the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), you will need to manually configure the activation. This can be done one of two ways: - * **Option 1:** Set the activation time in the `rollup.json` for `op-node`. You will still need to set the `override.granite` flag in `op-geth` if you use this option. + * **Option 1:** Set the activation time in the `rollup.json` for `op-node`. You will still need to set the `override.holocene` flag in `op-geth` if you use this option. * **Option 2:** Set the activation time via overrides (CLI) in both `op-node` and `op-geth`. These will need to be set on `op-node` and `op-geth` for the sequencer and all other nodes. ### Verify Your Configuration From ba57f971eae2e31d992b187a23545050d8d144fe Mon Sep 17 00:00:00 2001 From: soyboy Date: Wed, 13 Nov 2024 16:49:21 +0700 Subject: [PATCH 03/12] updating hf page --- .../node-operators/network-upgrades.mdx | 120 +++--------------- pages/builders/notices.mdx | 2 + pages/builders/notices/holocene-changes.mdx | 29 ++--- words.txt | 16 --- 4 files changed, 31 insertions(+), 136 deletions(-) diff --git a/pages/builders/node-operators/network-upgrades.mdx b/pages/builders/node-operators/network-upgrades.mdx index 290021c27..24979c4ca 100644 --- a/pages/builders/node-operators/network-upgrades.mdx +++ b/pages/builders/node-operators/network-upgrades.mdx @@ -1,7 +1,7 @@ --- title: Network upgrades lang: en-US -description: Learn more about how network upgrades work and how to keep your nodes up to date. +description: Learn more about Superchain network activations. --- import Image from 'next/image' @@ -9,113 +9,23 @@ import { Steps, Callout } from 'nextra/components' # Network upgrade overview -This section has information on how to upgrade your Mainnet and Testnet nodes -for new network upgrades. The network upgrade naming scheme after the Bedrock -upgrade has a geology themed name based on the next letter in the english -alphabet. +This page has the hardfork activation timestamps and the links to the details outlined in the specs. +It also outlines the hardfork release process. +The network upgrade naming scheme after the Bedrock upgrade has a geology themed name based on the next letter in the english alphabet. ## Activations -Network upgrades are activated by timestamps. Failing to upgrade your node -before the timestamp will cause a chain divergence. You will need to resync -your node to reconcile the chain. Optimistic activation times refer to times -that are pending governance approval. - -| Upgrade | Governance Approval | [OP Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [OP Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | -| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| [Granite](https://specs.optimism.io/protocol/granite/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | -| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | -| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | -| [Delta](https://specs.optimism.io/protocol/delta/overview.html) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | -| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | -| Bedrock | ([https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548)) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | - -## Summary of changes - -These are the summaries of each network upgrade changes ordered by the most -recent activation. These are a reflection of the [Superchain Upgrades Specifications](https://specs.optimism.io/protocol/superchain-upgrades.html) - -### [Granite](https://specs.optimism.io/protocol/granite/overview.html) - -The Granite upgrade limits `bn256Pairing` precompile input size and reduces the Channel Timeout. - -* [Limit `bn256Pairing` precompile input size](https://specs.optimism.io/protocol/granite/exec-engine.html#bn256pairing-precompile-input-restriction) -* [Reduce Channel Timeout to 50](https://specs.optimism.io/protocol/granite/derivation.html#reduce-channel-timeout) - -### [Fjord](https://specs.optimism.io/protocol/fjord/overview.html) - -The Fjord upgrade includes the RIP-7212 precompile, FastLZ gas pricing, Brotli channel compression, and several protocol parameter changes. - -* [RIP-7212: Precompile for secp256r1](https://specs.optimism.io/protocol/precompiles.html#P256VERIFY) -* [Brotli channel compression](https://specs.optimism.io/fjord/exec-engine.html#fees) -* FastLZ gas pricing - * [FastLZ L1 fee cost calculation](https://specs.optimism.io/fjord/exec-engine.html#fees) - * [Upgraded GasPriceOracle to compute FastLZ](https://specs.optimism.io/fjord/derivation.html#gaspriceoracle-deployment) - * [L1 gas cost changes](https://specs.optimism.io/fjord/predeploys.html#l1-gas-usage-estimation) -* Protocol parameter changes - * [Max sequencer drift becomes constant](https://specs.optimism.io/fjord/derivation.html#constant-maximum-sequencer-drift) - * [Channel constant increases](https://specs.optimism.io/fjord/derivation.html#increasing-max_rlp_bytes_per_channel-and-max_channel_bank_size) -* [Fjord hardfork activation block](https://specs.optimism.io/fjord/derivation.html#network-upgrade-automation-transactions) - -### [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html) - -The Ecotone upgrade contains the Dencun upgrade from L1, and adopts EIP-4844 blobs for data-availability. - -Cancun (Execution Layer): - -* [EIP-1153: Transient storage opcodes](https://eips.ethereum.org/EIPS/eip-1153) -* [EIP-4844: Shard Blob Transactions](https://eips.ethereum.org/EIPS/eip-4844) -* [Blob transactions are disabled](https://specs.optimism.io/protocol/exec-engine.html#ecotone-disable-blob-transactions) -* [EIP-4788: Beacon block root in the EVM](https://eips.ethereum.org/EIPS/eip-4788) -* [The L1 beacon block root is embedded into L2](https://specs.optimism.io/protocol/exec-engine.html#ecotone-beacon-block-root) -* [The Beacon roots contract deployment is automated](https://specs.optimism.io/protocol/derivation.html#ecotone-beacon-block-roots-contract-deployment-eip-4788) -* [EIP-5656: MCOPY - Memory copying instruction](https://eips.ethereum.org/EIPS/eip-5656) -* [EIP-6780: SELFDESTRUCT only in same transaction](https://eips.ethereum.org/EIPS/eip-6780) -* [EIP-7516: BLOBBASEFEE opcode](https://eips.ethereum.org/EIPS/eip-7516) -* [BLOBBASEFEE always pushes 1 onto the stack](https://specs.optimism.io/protocol/exec-engine.html#ecotone-disable-blob-transactions) - -Deneb (Consensus Layer): *not applicable to L2* - -* [EIP-7044: Perpetually Valid Signed Voluntary Exits](https://eips.ethereum.org/EIPS/eip-7044) -* [EIP-7045: Increase Max Attestation Inclusion Slot](https://eips.ethereum.org/EIPS/eip-7045) -* [EIP-7514: Add Max Epoch Churn Limit](https://eips.ethereum.org/EIPS/eip-7514) - -Data Availability (DA) upgrade: - -* Blobs Data Availability: support blobs DA the [L1 Data-retrieval stage](https://specs.optimism.io/protocol/derivation.html#ecotone-blob-retrieval). -* Rollup fee update: support blobs DA in [L1 Data Fee computation](https://specs.optimism.io/protocol/exec-engine.html#ecotone-l1-cost-fee-changes-eip-4844-da) -* Auto-upgrading and extension of the [L1 Attributes Predeployed Contract](https://specs.optimism.io/protocol/deposits.html#ecotone-l1block-upgrade) - (also known as `L1Block` predeploy) - -### [Delta](https://specs.optimism.io/protocol/delta/overview.html) - -The Delta upgrade consists of a single consensus-layer feature: [Span Batches](https://specs.optimism.io/protocol/delta/span-batches.html). - -The Delta upgrade uses a *L2 block-timestamp* activation-rule, and is specified only in the rollup-node (`delta_time`). - -### [Canyon](https://specs.optimism.io/protocol/canyon/overview.html) - -The Canyon upgrade contains the Shapella upgrade from L1 and some minor protocol fixes. - -* [EIP-3651: Warm COINBASE](https://eips.ethereum.org/EIPS/eip-3651) -* [EIP-3855: PUSH0 instruction](https://eips.ethereum.org/EIPS/eip-3855) -* [EIP-3860: Limit and meter initcode](https://eips.ethereum.org/EIPS/eip-3860) -* [EIP-4895: Beacon chain push withdrawals as operations](https://eips.ethereum.org/EIPS/eip-4895) -* [Withdrawals are prohibited in P2P Blocks](https://specs.optimism.io/protocol/rollup-node-p2p.html#block-validation) -* [Withdrawals should be set to the empty array with Canyon](https://specs.optimism.io/protocol/derivation.html#building-individual-payload-attributes) -* [EIP-6049: Deprecate SELFDESTRUCT](https://eips.ethereum.org/EIPS/eip-6049) -* [Modifies the EIP-1559 Denominator](https://specs.optimism.io/protocol/exec-engine.html#1559-parameters) -* [Channel Ordering Fix](https://specs.optimism.io/protocol/derivation.html#reading) -* [Adds the deposit nonce & deposit nonce version to the deposit receipt hash](https://specs.optimism.io/protocol/deposits.html#deposit-receipt) -* [Deploys the create2Deployer to `0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2`](https://specs.optimism.io/protocol/predeploys.html#create2deployer) - -The Canyon upgrade uses a *L2 block-timestamp* activation-rule, and is specified in both the -rollup-node (`canyon_time`) and execution engine (`config.canyonTime`). Shanghai time in the -execution engine should be set to the same time as the Canyon time. - -### Bedrock - -The Bedrock upgrade transitioned the OP Stack from its legacy design to a modern modular architecture. This new design separates the OP Stack into distinct consensus, execution, and settlement layers, enabling more efficient integration of future improvements and facilitating the growth of a Superchain ecosystem. +Network upgrades are activated by timestamps. Failing to upgrade your OP Stack software before the timestamp will cause a chain divergence and you will need to resync the chain. Optimistic activation times refer to times that are pending governance approval. + +| Upgrade | Governance Approval | [Mainnet Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml) | [Sepolia Activations](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) | +| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | +| [Holocene](https://specs.optimism.io/protocol/holocene/overview.html) | TBD | TBD | Tue Nov 26 15:00:00 UTC 2024 (`1732633200`) | +| [Granite](https://specs.optimism.io/protocol/granite/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-10-granite-network-upgrade/8733) | Wed Sep 11 16:00:01 UTC 2024 (`1726070401`) around block `125235812` | Mon Aug 12 16:00:00 UTC 2024 (`1723478400`) around block `15837930` | +| [Fjord](https://specs.optimism.io/protocol/fjord/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-9-fjord-network-upgrade/8236) | Wed Jul 10 16:00:01 UTC 2024 (`1720627201`) around block `122514212` | Wed May 29 16:00:00 UTC 2024 (`1716998400`) around block `12597930` | +| [Ecotone](https://specs.optimism.io/protocol/ecotone/overview.html) | [approved](https://gov.optimism.io/t/upgrade-proposal-5-ecotone-network-upgrade/7669) | Thu Mar 14 00:00:01 UTC 2024 (`1710374401`) around block `117387812` | Wed Feb 21 17:00:00 UTC 2024 (`1708534800`) around block `8366130` | +| [Delta](https://specs.optimism.io/protocol/delta/overview.html) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-3-delta-network-upgrade/7310) | Thu Feb 22 00:00:00 UTC 2024 (`1708560000`) around block `116480612` | Fri Dec 22 00:00:00 UTC 2023 (`1703203200`) around block `5700330` | +| [Canyon](https://specs.optimism.io/protocol/canyon/overview.html) | [approved](https://gov.optimism.io/t/final-upgrade-proposal-2-canyon-network-upgrade/7088) | Thu Jan 11 17:00:01 UTC 2024 (`1704992401`) around block `114696812` | Tue Nov 14 17:00:00 UTC 2023 (`1699981200`) around block `4089330` | +| Bedrock | [approved](https://gov.optimism.io/t/final-upgrade-1-bedrock-protocol-upgrade-v2/5548) | Tue Jun 06 2023 16:28:23 UTC (`1686079703`) at block `105235063` | N/A | ## Upgrade process diff --git a/pages/builders/notices.mdx b/pages/builders/notices.mdx index 27aaaa0ab..5ca3a4b7f 100644 --- a/pages/builders/notices.mdx +++ b/pages/builders/notices.mdx @@ -11,5 +11,7 @@ import { Card, Cards } from 'nextra/components' Documentation covering Sdk Deprecation in the Notices section of the OP Stack ecosystem. + + diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index 54b2a560b..d88d8f010 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -12,44 +12,43 @@ This page outlines breaking changes related to the Holocene network upgrade for If you experience difficulty at any stage of this process, please reach out to [developer support](https://github.com/ethereum-optimism/developers/discussions). -The Holocene upgrade for the Sepolia Superchain will be activated at **Tue Nov 26 at 15:00:00 UTC (unix timestamp** `1732633200`). + The Holocene upgrade for the Sepolia Superchain will be activated at **Tue Nov 26 at 15:00:00 UTC** (`1732633200`). -The Holocene upgrade for the Mainnet Superchain is optimistically scheduled for **Thu 9 Jan 2025 18:00:01 UTC**, pending governance approval. + The Holocene upgrade for the Mainnet Superchain is optimistically scheduled for **Thu 9 Jan 2025 18:00:01 UTC**, pending governance approval. ## What's included in Holocene Holocene contains two changes: -- **Holocene block derivation**: a set of changes that render the derivation pipeline stricter and simpler, improving worst-case scenarios for the Fault Proof System and Interoperability. -- **EIP-1559 configurability**: The elasticity and denominator EIP-1559 parameters become configurable via the `SystemConfig` L1 contract, allowing the gas target and gas limit to be configured independently. +* **Holocene block derivation**: a set of changes that render the derivation pipeline stricter and simpler, improving worst-case scenarios for the Fault Proof System and Interoperability. +* **EIP-1559 configurability**: The elasticity and denominator EIP-1559 parameters become configurable via the `SystemConfig` L1 contract, allowing the gas target and gas limit to be configured independently. - For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html). +For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html). ## For chain operators Chain operators have to upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides. -TODO: is this a must? for mode, metal, and zora sepolia they're on op-contracts/v1.3.0; but they're also opted into superchain wide upgrades. +TODO: is this a must? for mode, metal, and zora sepolia they're on op-contracts/v1.3.0; but they're also opted into superchain wide upgrades. Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1). The updated `SystemConfig` implementations are deployed at addresses -- Sepolia: TBD -- Mainnet: TBD +* Sepolia: TBD +* Mainnet: TBD -Chain operators need to update their proxy contracts to point to these new implementations. The following upgrade script can be used to facilitate the upgrade: https://github.com/ethereum-optimism/optimism/pull/12878 +Chain operators need to update their proxy contracts to point to these new implementations. The following upgrade script can be used to facilitate the upgrade: [https://github.com/ethereum-optimism/optimism/pull/12878](https://github.com/ethereum-optimism/optimism/pull/12878) - -### For fault proof enabled chains +### For fault proof enabled chains Since the Holocene upgrade changes the execution and derivation rules, the version of `op-program` used in the fault proof system has to be upgraded to a version that includes the Holocene activation date for the chain. The `op-program` version used is specified via the `faultGameAbsolutePrestate` setting, deployed as part of `FaultDisputeGame` and `PermissionedDisputeGame` contracts. Additionally, the `MIPS` contract must be upgraded to support additional calls made by the new `op-program`. The `FaultDisputeGame` and `PermissionedDisputeGame` contracts must be deployed separately for each chain. The `MIPS` contract implementation can be shared by all chains and is deployed at: -- Sepolia: TBD -- Mainnet: TBD +* Sepolia: TBD +* Mainnet: TBD -Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The following upgrade script can be used to facilitate the upgrade: https://github.com/ethereum-optimism/optimism/pull/12878 +Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The following upgrade script can be used to facilitate the upgrade: [https://github.com/ethereum-optimism/optimism/pull/12878](https://github.com/ethereum-optimism/optimism/pull/12878) ## For node operators @@ -83,4 +82,4 @@ These following steps are necessary for every node operator: * `op-node` and `op-geth` will log their configurations at startup * Check that the Granite time is set to `activation-timestamp` in the op-node startup logs * Check that the Granite time is set to `activation-timestamp` in the op-geth startup logs - \ No newline at end of file + diff --git a/words.txt b/words.txt index f5ae76fbc..9ff8f1a1e 100644 --- a/words.txt +++ b/words.txt @@ -10,7 +10,6 @@ Allnodes Allocs allocs ANDI -Ankr Apeworx Arweave authrpc @@ -23,7 +22,6 @@ BGTZ Biconomy birthdate BLEZ -BLOBBASEFEE BLOBPOOL blobpool blobspace @@ -75,7 +73,6 @@ DATACAP datacap DATADIR datadir -Dencun Devnet devnet devnets @@ -150,13 +147,11 @@ holesky IERC IGNOREPRICE ignoreprice -Immunefi implicity Inator inator INFLUXDBV influxdbv -initcode interchain IPCDISABLE ipcdisable @@ -186,7 +181,6 @@ MAXPENDPEERS maxpendpeers MAXPRICE maxprice -MCOPY MEMPROFILERATE memprofilerate Merkle @@ -200,7 +194,6 @@ minsuggestedpriorityfee Mintable Mintplex MIPSEVM -Mitigations Monitorism Moralis Mordor @@ -295,8 +288,6 @@ Proxied Proxyd proxyd pseudorandomly -Pyth -Pyth's QRNG Quicknode quicknode @@ -329,16 +320,10 @@ runbooks RWAs safedb Schnorr -secp -SELFDESTRUCT -SEPOLIA -Sepolia -sepolia seqnr SEQUENCERHTTP sequencerhttp serv -Shapella signup SLLV SLTI @@ -404,7 +389,6 @@ VMDEBUG vmdebug VMODULE vmodule -voxel Warpcast xlarge XORI From 2b574b5be6dc421579fcbe76b14b08ab6435e036 Mon Sep 17 00:00:00 2001 From: soyboy Date: Wed, 13 Nov 2024 16:59:54 +0700 Subject: [PATCH 04/12] resolving todo --- pages/builders/notices/holocene-changes.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index d88d8f010..a733e725d 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -30,9 +30,7 @@ For more information on the Holocene implementation details, please review [Holo Chain operators have to upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides. -TODO: is this a must? for mode, metal, and zora sepolia they're on op-contracts/v1.3.0; but they're also opted into superchain wide upgrades. - -Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1). The updated `SystemConfig` implementations are deployed at addresses +Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1) to utilize the EIP-1559 configurability. The updated `SystemConfig` implementations are deployed at addresses: * Sepolia: TBD * Mainnet: TBD From 011ae170293a76da4a30a795c803ceb093751981 Mon Sep 17 00:00:00 2001 From: soyboy Date: Wed, 13 Nov 2024 17:02:19 +0700 Subject: [PATCH 05/12] we really need to fix this linter thing --- words.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/words.txt b/words.txt index 9ff8f1a1e..185655d9c 100644 --- a/words.txt +++ b/words.txt @@ -397,3 +397,12 @@ ZKPs ZKVM Zora zora +Sepolia +voxel +SEPOLIA +sepolia +Pyth +Pyth's +Ankr +Mitigations +Immunefi From 10023787af21f11ced211ab4d2dded7131973f5d Mon Sep 17 00:00:00 2001 From: soyboy Date: Tue, 19 Nov 2024 21:09:49 +0800 Subject: [PATCH 06/12] small clean up --- pages/builders/notices/holocene-changes.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index a733e725d..a19fd9a26 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -28,14 +28,14 @@ For more information on the Holocene implementation details, please review [Holo ## For chain operators -Chain operators have to upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides. +Chain operators should upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides. Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1) to utilize the EIP-1559 configurability. The updated `SystemConfig` implementations are deployed at addresses: * Sepolia: TBD * Mainnet: TBD -Chain operators need to update their proxy contracts to point to these new implementations. The following upgrade script can be used to facilitate the upgrade: [https://github.com/ethereum-optimism/optimism/pull/12878](https://github.com/ethereum-optimism/optimism/pull/12878) +Chain operators need to update their proxy contracts to point to these new implementations. An upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). Note that it is fine to upgrade the SystemConfig after the Holocene activation. You need to upgrade if you want to reconfigure your EIP-1559 parameters. ### For fault proof enabled chains @@ -46,7 +46,7 @@ The `FaultDisputeGame` and `PermissionedDisputeGame` contracts must be deployed * Sepolia: TBD * Mainnet: TBD -Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The following upgrade script can be used to facilitate the upgrade: [https://github.com/ethereum-optimism/optimism/pull/12878](https://github.com/ethereum-optimism/optimism/pull/12878) +Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The same upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). ## For node operators @@ -57,8 +57,8 @@ These following steps are necessary for every node operator: ### Update to the latest release - * [`op-geth`](FIND_CORRECT_LINK) - * [`op-node`](FIND_CORRECT_LINK) + * [`op-node`, `op-batcher`, and `op-proposer` at `v1.10.0`]() + * [`op-geth` at `v1.101411.2`]() ### Configure the Holocene activation date @@ -78,6 +78,6 @@ These following steps are necessary for every node operator: 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 Granite time is set to `activation-timestamp` in the op-node startup logs - * Check that the Granite time is set to `activation-timestamp` in the op-geth startup logs + * Check that the Holocene time is set to `activation-timestamp` in the op-node startup logs + * Check that the Holocene time is set to `activation-timestamp` in the op-geth startup logs From daf7f2022d83c2a5c2a171dfdfb8a8bf32c89c56 Mon Sep 17 00:00:00 2001 From: soyboy <85043086+sbvegan@users.noreply.github.com> Date: Wed, 20 Nov 2024 00:09:28 +0800 Subject: [PATCH 07/12] Update pages/builders/notices/holocene-changes.mdx Co-authored-by: Matt Solomon --- pages/builders/notices/holocene-changes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index a19fd9a26..aa5438a99 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -35,7 +35,7 @@ Besides this, chain operators must upgrade their chain's `SystemConfig` to the l * Sepolia: TBD * Mainnet: TBD -Chain operators need to update their proxy contracts to point to these new implementations. An upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). Note that it is fine to upgrade the SystemConfig after the Holocene activation. You need to upgrade if you want to reconfigure your EIP-1559 parameters. +Chain operators need to update their proxy contracts to point to these new implementations. An upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). Note that it is recommended to upgrade the SystemConfig after the Holocene activation. You need to upgrade if you want to reconfigure your EIP-1559 parameters. ### For fault proof enabled chains From 204bd67ad0c88b2e881fad8150ecf2d99089535b Mon Sep 17 00:00:00 2001 From: soyboy Date: Wed, 20 Nov 2024 06:57:50 +0800 Subject: [PATCH 08/12] updating links --- pages/builders/notices/holocene-changes.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index aa5438a99..786bdcafb 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -30,12 +30,12 @@ For more information on the Holocene implementation details, please review [Holo Chain operators should upgrade their nodes ahead of the activation times to a release that contains the Holocene changes and has the activation times for their chains baked in, or set the activation times manually via overrides. -Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.1 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.1) to utilize the EIP-1559 configurability. The updated `SystemConfig` implementations are deployed at addresses: +Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.2 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.2) to utilize the EIP-1559 configurability. The updated `SystemConfig` implementations are deployed at addresses: * Sepolia: TBD * Mainnet: TBD -Chain operators need to update their proxy contracts to point to these new implementations. An upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). Note that it is recommended to upgrade the SystemConfig after the Holocene activation. You need to upgrade if you want to reconfigure your EIP-1559 parameters. +Chain operators need to update their proxy contracts to point to these new implementations. An upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0-rc.2/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). Note that it is recommended to upgrade the SystemConfig after the Holocene activation. You need to upgrade if you want to reconfigure your EIP-1559 parameters. ### For fault proof enabled chains @@ -46,7 +46,7 @@ The `FaultDisputeGame` and `PermissionedDisputeGame` contracts must be deployed * Sepolia: TBD * Mainnet: TBD -Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The same upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). +Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The same upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0-rc.2/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). ## For node operators @@ -57,8 +57,8 @@ These following steps are necessary for every node operator: ### Update to the latest release - * [`op-node`, `op-batcher`, and `op-proposer` at `v1.10.0`]() - * [`op-geth` at `v1.101411.2`]() + * [`op-node`, `op-batcher`, and `op-proposer` at `v1.10.0`](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.10.0) + * [`op-geth` at `v1.101411.2`](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101411.2) ### Configure the Holocene activation date From 8c5acd7338c79df42223f51bf2f017ce86302488 Mon Sep 17 00:00:00 2001 From: soyboy <85043086+sbvegan@users.noreply.github.com> Date: Wed, 20 Nov 2024 07:00:13 +0800 Subject: [PATCH 09/12] Update pages/builders/notices/holocene-changes.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/builders/notices/holocene-changes.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index 786bdcafb..c2894c27d 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -19,10 +19,11 @@ If you experience difficulty at any stage of this process, please reach out to [ ## What's included in Holocene -Holocene contains two changes: +Holocene contains three changes: * **Holocene block derivation**: a set of changes that render the derivation pipeline stricter and simpler, improving worst-case scenarios for the Fault Proof System and Interoperability. * **EIP-1559 configurability**: The elasticity and denominator EIP-1559 parameters become configurable via the `SystemConfig` L1 contract, allowing the gas target and gas limit to be configured independently. +* **MIPS contract upgrade**: Updates to support additional calls made by the new `op-program` version. For more information on the Holocene implementation details, please review [Holocene specification](https://specs.optimism.io/protocol/holocene/overview.html). From 37f0aea4d35fad06f58d8918a735c1250d1ea0b9 Mon Sep 17 00:00:00 2001 From: soyboy <85043086+sbvegan@users.noreply.github.com> Date: Wed, 20 Nov 2024 07:11:03 +0800 Subject: [PATCH 10/12] Update pages/builders/node-operators/network-upgrades.mdx Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- pages/builders/node-operators/network-upgrades.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/builders/node-operators/network-upgrades.mdx b/pages/builders/node-operators/network-upgrades.mdx index 24979c4ca..e82206f6a 100644 --- a/pages/builders/node-operators/network-upgrades.mdx +++ b/pages/builders/node-operators/network-upgrades.mdx @@ -9,9 +9,9 @@ import { Steps, Callout } from 'nextra/components' # Network upgrade overview -This page has the hardfork activation timestamps and the links to the details outlined in the specs. -It also outlines the hardfork release process. -The network upgrade naming scheme after the Bedrock upgrade has a geology themed name based on the next letter in the english alphabet. +This page provides hardfork activation timestamps and links to detailed specifications. +The documentation outlines the hardfork release process. +The network upgrade naming scheme after the Bedrock upgrade follows a geology theme based on the next letter in the English alphabet. ## Activations From 0a112fb9ce074119ef7db6daeea4274348876d54 Mon Sep 17 00:00:00 2001 From: soyboy <85043086+sbvegan@users.noreply.github.com> Date: Wed, 20 Nov 2024 12:15:33 +0800 Subject: [PATCH 11/12] Apply suggestions from code review Co-authored-by: Sebastian Stammler --- pages/builders/notices/holocene-changes.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index c2894c27d..473b6deb6 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -33,7 +33,7 @@ Chain operators should upgrade their nodes ahead of the activation times to a re Besides this, chain operators must upgrade their chain's `SystemConfig` to the latest OP Contracts [v1.8.0-rc.2 release](https://github.com/ethereum-optimism/optimism/releases/tag/op-contracts%2Fv1.8.0-rc.2) to utilize the EIP-1559 configurability. The updated `SystemConfig` implementations are deployed at addresses: -* Sepolia: TBD +* Sepolia: `0x29d06Ed7105c7552EFD9f29f3e0d250e5df412CD` * Mainnet: TBD Chain operators need to update their proxy contracts to point to these new implementations. An upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0-rc.2/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). Note that it is recommended to upgrade the SystemConfig after the Holocene activation. You need to upgrade if you want to reconfigure your EIP-1559 parameters. @@ -44,7 +44,7 @@ Since the Holocene upgrade changes the execution and derivation rules, the versi The `FaultDisputeGame` and `PermissionedDisputeGame` contracts must be deployed separately for each chain. The `MIPS` contract implementation can be shared by all chains and is deployed at: -* Sepolia: TBD +* Sepolia: `0x6f86b56d26F60a86Ccd13048993C1cE410565DC1` * Mainnet: TBD Chain operators need to update the `DisputeGameFactory` to use the new `FaultDisputeGame` and `PermissionedDisputeGame` contracts by calling `DisputeGameFactory.setImplementation`. The same upgrade script in the monorepo can be used to facilitate the upgrade, please follow the instructions in this [README](https://github.com/ethereum-optimism/optimism/blob/op-contracts/v1.8.0-rc.2/packages/contracts-bedrock/scripts/upgrades/holocene/README.md). @@ -58,7 +58,7 @@ These following steps are necessary for every node operator: ### Update to the latest release - * [`op-node`, `op-batcher`, and `op-proposer` at `v1.10.0`](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.10.0) + * [`op-node` at `v1.10.0`](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.10.0) * [`op-geth` at `v1.101411.2`](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101411.2) ### Configure the Holocene activation date From c33758e6e49e7238473654fdc6cdda6a485c98d1 Mon Sep 17 00:00:00 2001 From: soyboy Date: Wed, 20 Nov 2024 12:16:24 +0800 Subject: [PATCH 12/12] adding metal sepolia --- pages/builders/notices/holocene-changes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/builders/notices/holocene-changes.mdx b/pages/builders/notices/holocene-changes.mdx index 473b6deb6..7fd4d0aee 100644 --- a/pages/builders/notices/holocene-changes.mdx +++ b/pages/builders/notices/holocene-changes.mdx @@ -66,7 +66,7 @@ These following steps are necessary for every node operator: If you are operating a node for an OP Chain that have opted into the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), the Holocene activation date is part of the `op-node` and `op-geth` nodes. So, no action is needed for the sequencer after upgrading to the latest release. Please skip to [Step 3: Verify Your Configuration](#verify-your-configuration). - For Sepolia that is: `OP Sepolia`, `Base Sepolia`, `Mode Sepolia`, and `Zora Sepolia`. + For Sepolia that is: `OP Sepolia`, `Base Sepolia`, `Mode Sepolia`, `Zora Sepolia`, and `Metal Sepolia`. For node operators of not included in the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), you will need to manually configure the activation. This can be done one of two ways: