Please note that this notice page was updated March 11th, 2025. There was a bug found in previous op-node releases where the L1 Block’s blob base fee (for the sake of computing the L1 fees) is calculated with pre-Prague=Cancun blob schedule parameters, instead of using the Prague parameters. This bug has been fixed in the latest release of op-node.This is not a critical issue on any OP Sepolia chain. However, when L1 blob base fees rise to 100 Mwei or higher on Sepolia, there is a temporary liveness risk, because we’d be overcharge L1 fees. Essentially, our L1 cost computation now overcharges by an exponential of 1.5, BBF_Cancun =
BBF_Prague^1.5
(where BBF=blob base fee).You must update your Sepolia nodes to the latest release of op-node and schedule a hardfork activation time to avoid this issue on your network. There are new instructions in the node operator section to help you mitigate this issue.See this notice page for more information: Superchain testnets’ blob fee bug.- 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.
- 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. The upcoming Isthmus hardfork will contain all Prague features, you can track our progress in this project board.
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:
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?
Pectra contains a variety of EIPs, some of which apply to the OP Stack; others do not. The following EIPs are included in Pectra as outlined in the Pectra Devnet 5 notes:- EIP-2537: Precompile for BLS12-381 curve operations
- EIP-2935: Save historical block hashes in state
- EIP-6110: Supply validator deposits on chain
- EIP-7002: Execution layer triggerable withdrawals
- EIP-7251: Increase the MAX_EFFECTIVE_BALANCE
- EIP-7549: Move committee index outside Attestation
- EIP-7623: Increase calldata cost
- EIP-7685: General purpose execution layer requests
- EIP-7691: Blob throughput increase
- EIP-7702: Set EOA account code
- EIP-7840: Add blob schedule to EL config files
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
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 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
atv1.12.0
op-geth
atv1.101503.0
op-reth
atv1.2.0
also includes L1 Pectra support.
Schedule your hardfork activation time when upgrading your op-node binaries to ensure your network uses the correct fee calculation. Please review the Superchain Registry configurations to determine if your network needs to coordinate this independently from the Superchain activation time.
- Option 1: Set the
pectrablobschedule
activation time in therollup.json
forop-node
. - Option 2: Set the activation time via overrides (CLI) in
op-node
. These will need to be set onop-node
for the sequencer and all other nodes.
op-geth
, but you will need to update it to the latest release.
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:1
Update your node binaries
Follow the guidance outlined in the Node Operator section to update your nodes to the latest releases.
2
Update your batcher and proposer
Update your binaries to:
3
Double-check your fee scalars
For fault proof enabled chains
The following instructions assume your chain is on the latest contract release
op-contracts/v1.8.0
and has Holocene activated.op-challenger
binary to op-challenger/v1.3.2
.
The following steps are to update your absolute prestate with new dispute game contracts. This is absolutely necessary for chains running permissionless fault proofs. For chains running the Fault Proof System with permissioned games you can skip this section because games will not be played out and the absolute prestate is not used.
The Pectra upgrade changes the derivation rules, permissionless fault proof chains need to upgrade the op-program
version used in the fault proof system to support these changes. The op-program
version used is specified via the faultGameAbsolutePrestate
setting, deployed as part of FaultDisputeGame
and PermissionedDisputeGame
contracts.
1
Verify the new absolute prestate
The absolute prestate is generated with the op-program/v1.5.0-rc.4. You can use this new absolute prestate (You should expect the following output at the end of the command:
0x0354eee87a1775d96afee8977ef6d5d6bd3612b256170952a01bf1051610ee01
) for the following chains:- Sepolia: Base, OP, Metal, Mode, Zora, Ethernity, Unichain, Ink, Minato (Soneium)
- Mainnet: Base, OP, Orderly, Lyra, Metal, Mode, Zora, Lisk, Ethernity, Binary, Ink, Unichain, Soneium
op-program/v1.5.0-rc.4
tag:2
Upload your new preimage file
During the previous step, you also generated the preimage of the absolute prestate, which is basically the op-program serialized into a binary file. You’ll find that new file at
optimism/op-program/bin/prestate.bin.gz
. Rename that file to have the absolute prestate hash as the filename so it looks like 0x0354eee87a1775d96afee8977ef6d5d6bd3612b256170952a01bf1051610ee01.bin.gz
.Upload that file to where you’re storing your other absolute preimage files. This should be the location where you’re pointing your --cannon-prestates-url
at. The op-challenger
will grab this file and use it when it needs to challenge games.3
Deploy new dispute game contracts
You will then take the absolute prestate and deploy new
FaultDisputeGame
and PermissionedDisputeGame
contracts with that value. You can reuse the Holocene script to deploy the new contracts. The only change you will need to make is to update the absolutePrestate
value in your deploy-config. Alternatively we will be releasing an OPPrestateUpdater
that can be used to deploy the new contracts.4
Update the DisputeGameFactory
You will then need to update the
DisputeGameFactory
to point to the new FaultDisputeGame
and PermissionedDisputeGame
contracts by calling DisputeGameFactory.setImplementation
. You can utilize this template to generate the transaction and validation script for this step. Before executing, you will need to update your op-challenger.5
Execute the upgrade
Once your
op-challenger
is ready with the new preimage, you can execute the “Set Dispute Game Implementation” transaction. Please simulate and validate that the expected output prior to executing the transaction.