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