Releases: ethereum-optimism/optimism
op-node/v1.13.2 - Isthmus Mainnet
Isthmus Mainnet
Important
This is a required upgrade for any Mainnet Superchain node by May 9 as it contains the Isthmus activation on that date. It is unnecessary for other networks.
This is the Isthmus release for the Mainnet Superchain. It schedules the activation of the Isthmus fork on Fri May 9 16:00:00 UTC 2025 (unix timestamp 1746806401).
The following Mainnet chains have the Isthmus upgrade scheduled at this timestamp: arena-z, base, bob, ethernity, ink, lisk, lyra, metal, mint, mode, op, orderly, polynomial, snax, soneium, tbn, unichain, zora. It is mandatory to upgrade nodes for those chains before May 9.
🤝 The corresponding mandatory op-geth release is v1.101503.4.
Chain operators also need to upgrade their batchers to op-batcher/v1.12.0 before activating Isthmus on their chains.
Important
Make sure the batcher is restarted at least once after the sequencers are running with this release, so that it can fetch the latest chain config including the Isthmus activation at startup.
What's Changed
- go: Prepare Isthmus Mainnet release by @sebastianst in #15363
Full Changelog: op-node/v1.13.1...op-node/v1.13.2
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.2
Contributors
Assets 2
op-challenger/v1.4.0
Overview
This release of op-challenger fixes a medium severity bug related to EIP-4844 blob data handling. It is a required upgrade for all users.
What's Changed
- Rework blob preimage handling in
op-challengerandop-programhost and client. This fixes an issue where theop-challengerwould push up the wrong blob data to the preimage oracle contract.
Full Changelog: op-challenger/v1.3.3...op-challenger/v1.4.0
🚢 Docker Image:
op-node v1.13.1 - Worldchain Sepolia Fix
This release fixes the Worldchain Sepolia genesis configuration (#15319). It is not required for any other chain.
Important
For Sepolia Superchain nodes, please look at the required prior release v1.13.0.
🤝 The corresponding op-geth release is v1.101503.3.
This release also provides the flag for setting/overriding the Isthmus time (--override.isthmus) which was previously missing (#15291).
What's Changed
- op-service: cleanup eth.ChainID type, remove uint32 index legacy, add sort method by @protolambda in #15148
- go: RPC metrics by default by @protolambda in #15127
- op-node: add
FETCH_WITHDRAWAL_ROOT_FROM_STATEconfig var by @geoknee in #15150 - op-node,op-service: Add Isthmus & Interrop override flags by @sebastianst in #15291
- go: update [email protected] to fix Worldchain configs by @sebastianst in #15319
New Contributors
Full Changelog: op-node/v1.13.0...op-node/v1.13.1
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.1
Contributors
Assets 2
op-node v1.13.0 - Isthmus Sepolia
Isthmus Sepolia
Important
This is a required upgrade for any Sepolia Superchain node by Apr 17 as it contains the Isthmus activation on that date. It is optional for Mainnet chains.
This is the Isthmus release for the Sepolia Superchain. It schedules the activation of the Isthmus fork on Thu Apr 17 16:00:00 UTC 2025 (unix timestamp 1744905600).
The following Sepolia chains have the Isthmus upgrade scheduled at this timestamp: base, creator-chain-testnet, ethernity, ink, metal, mode, op, soneium-minato, unichain, zora, lisk. It is mandatory to upgrade nodes for those chains before Apr 17.
🤝 The corresponding mandatory op-geth release is v1.101503.2.
Chain operators also need to upgrade their batchers to op-batcher/v1.12.0 before activating Isthmus on their chains.
Warning
This release cannot be used to sync worldchain (both sepolia or mainnet) from genesis, or any partially synced node at or before Feb 20, 2025, when Worldchain updated the EIP-1559 parameters via the SystemConfig. It contains a wrong EIP-1559 elasticity at genesis that will lead to a BAD BLOCK during sync. Use the older release v1.12.2. We will publish a fix for Worldchain soon.
Note
The Isthmus activation date for the Mainnet Superchain isn't set yet. It won't be before Ethereum Mainnet activates Pectra, so not before May 7, which is the current tentative Pectra activation date.
Sequencing Window Recovery Mode (#14823)
This release contains a sequencer recovery mode to help in recovering from a sequencing window timeout. This behavior can be enabled with a flag/env var and/or via a new rpc call. More details can be found in the accompanying README section.
Stricter rollup.json requirement to contain the optimism chain config (#15041)
With this release, chains that are not part of the superchain-registry and hence use a rollup.json instead are now required to contain the new chain_op_config field in their rollup.json. It is not attempted any more to load this missing config from the execution client. This was buggy and never really worked. This breaking change was introduced with op-node/v1.11.0 - please refer to its release notes on the details of this breaking change.
What's Changed
- op-node: add sequencer "Recover Mode" feature by @geoknee in #14823
- op-node: remove
loadOrFetchChainConfigby @geoknee in #15041 - op-node: Don't reprocess unsafe payloads by @trianglesphere in #15038
- op-service: set implicit empty requests hash post-Isthmus by @sebastianst in #15105
- go: update op-geth dependency to prepare Isthmus Sepolia release by @sebastianst in #15135
New Contributors
- @dhyaniarun1993 made their first contribution in #14781
- @cocoyeal made their first contribution in #14748
- @VolodymyrBg made their first contribution in #14627
- @op-aaron made their first contribution in #14956
Full Changelog: op-node/v1.12.2...op-node/v1.13.0
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.13.0
Contributors
Assets 2
op-batcher v1.12.0 - Isthmus
Isthmus
Important
Chain operators need to upgrade their batchers before Isthmus activates on their chains. It is an optional upgrade until then.
This release adds support for SetCode transactions in (span) batches, which is a requirement for batching Isthmus chains.
The Sepolia Superchain will activate Isthmus on Apr 17, so those chain operators need to upgrade their batchers by then. See the op-node/v1.13.0 release notes for more details on the Isthmus Sepolia activation.
Note
The Isthmus activation date for the Mainnet Superchain isn't set yet. It won't be before Ethereum Mainnet activates Pectra, so not before May 7, which is the current tentative Pectra activation date.
What's Changed
- op-node/rollup/derive: implement SetCodeTx span batches by @meyer9 in #14197
- op-node/rollup/derive: validate to field non-nil for setcode txs by @meyer9 in #14882
- op-node/rollup/derive: Drop SetCodeTxs in pre-Isthmus batches by @sebastianst in #14877
- op-batcher: tweak godoc by @geoknee in #15030
- op-batcher: disallow blobs when Alt-DA is enabled by @zhiqiangxu in #15126
New Contributors
- @blockchaindevsh made their first contribution in #14709
- @dhyaniarun1993 made their first contribution in #14781
- @cocoyeal made their first contribution in #14748
- @VolodymyrBg made their first contribution in #14627
- @op-aaron made their first contribution in #14956
Full Changelog: op-batcher/v1.11.5...op-batcher/v1.12.0
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.12.0
Contributors
Assets 2
op-dispute-mon/v1.4.0
Overview
This is a minor release of op-dispute-mon that provide compatibility for upcoming contract changes. It is a required upgrade for all users.
What's Changed
- Update credit monitoring to prevent incorrect "Withdrawal request amount does not match credit" errors when contracts are updated to op-contracts/v2.0.0
- Initial support for interop dispute game types.
Full Changelog: op-dispute-mon/v1.3.0...op-dispute-mon/v1.4.0
🚢 Docker Image:
op-challenger/v1.3.3
Overview
This is a minor release of op-challenger that includes a fix to improve stability. It is an optional upgrade.
What's Changed
- Update op-program host to retry chain id queries. Without this fix, a single rpc request failure can cause the client to be unable to retrieve necessary data from the host, causing Cannon trace execution to fail.
Full Changelog: op-challenger/v1.3.2...op-challenger/v1.3.3
🚢 Docker Image:
op-node v1.12.2
Caution
If you're upgrading a Sepolia or Holesky node, you must take additional steps before upgrading to this (or a later) release!
Unless the chain of the node you're upgrading is in the following list of chains that have the Sepolia Pectra Blob Schedule fix already scheduled via their superchain-registry configuration, you must schedule the fix via rollup.json or overrides before upgrading!
List of chains that have the fix already scheduled:
soneium-minato, zora, op, unichain, base, mode, metal, creator-chain-testnet, ink, ethernity
If your chain is in this list, you must upgrade by 3/20 and no additional steps need to be taken before the upgrade.
If your chain is not in this list, you need to schedule the Pectra Blob Schedule fix to a timestamp that the chain's operator must decide on and publish to all its node operators. This release will fail at startup with a warning if you don't have the fix scheduled on a Sepolia or Holesky chain.
See the release notes for v1.12.0 for more details.
Caution
This release also supersedes any op-node/v1.11.x release for L1 Pectra Readiness. So mainnet node operators must also upgrade to this (or a later) release by the time Ethereum mainnet activates Pectra. No additional steps must be taken for mainnet chains.
Important
All node operators must also upgrade op-geth to v1.101503.1.
Important
This release is mandatory for Sepolia or Holesky chains. It is optional for mainnet chains who are already on op-node release v1.12.1, mandatory otherwise.
Pectra Blob Schedule Fix Kill-Switch (#14922)
This release adds a kill-switch to op-node to print an error at startup if the Pectra Blob Schedule Fix time is not set for a Sepolia or Holesky chain. The check only happens if the chain's genesis is before the Holesky/Sepolia Pectra activation time. The check can be disabled with a hidden flag.
The purpose of the kill-switch is to make sure that node operators don't accidentally upgrade their nodes without scheduling the fix because most Holesky and Sepolia chains were running a sequencer that ran into the Pectra Blob Schedule bug. So it's better to not start op-node in such cases at all rather than accidentally forking the chain.
What's Changed
- op-node/rollup/sequencing: No user txs in Isthmus & Interop upgrade block by @sebastianst in #14837
- op-node/rollup/derive: implement SetCodeTx span batches by @meyer9 in #14197
- op-node,op-service: cleanup block signing abstractions by @protolambda in #14874
- op-node/rollup/derive: validate to field non-nil for setcode txs by @meyer9 in #14882
- op-node/rollup/derive: Drop SetCodeTxs in pre-Isthmus batches by @sebastianst in #14877
- op-node: Add pectra blob schedule fix kill-switch by @sebastianst in #14922
Full Changelog: op-node/v1.12.1...op-node/v1.12.2
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.12.2
Contributors
Assets 2
op-deployer/v0.3.0-rc.5
op-node/v1.12.1
Caution
If you're upgrading a Sepolia or Holesky node, you must take additional steps before upgrading to this (or a later) release!
Unless the chain of the node you're upgrading is in the following list of chains that have the Sepolia Pectra Blob Schedule fix already scheduled via their superchain-registry configuration, you must schedule the fix via rollup.json or overrides before upgrading!
List of chains that have the fix already scheduled:
soneium-minato, zora, op, unichain, base, mode, metal, creator-chain-testnet, ink, ethernity
If your chain is in this list, you must upgrade by 3/20 and no additional steps need to be taken before the upgrade.
If your chain is not in this list, you need to schedule the Pectra Blob Schedule fix to a timestamp that the chain's operator must decide on and publish to all its node operators.
See the release notes for v1.12.0 for more details.
Caution
This release also supersedes any op-node/v1.11.x release for L1 Pectra Readiness. So mainnet node operators must also upgrade to this (or a later) release by the time Ethereum mainnet activates Pectra. No additional steps must be taken for mainnet chains.
Important
All node operators must also upgrade op-geth to v1.101503.1.
This release adds snaxchain config via op-geth and updates the startup banner to print the optional Pectra Blob Schedule fork (if set).
This is a recommended upgrade - ❗Sepolia chains see notice at the top ❗
What's Changed
- Include pectra blob schedule fork time in rollup config description. by @ajsutton in #14796
- all: update op-geth and SCR submodule by @geoknee in #14842
Full Changelog: op-node/v1.12.0...op-node/v1.12.1
🚢 Docker Image https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.12.1
