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
