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