v1.11.2

Preparing for Pectra breaking changes

Recommended to have a backup node before upgrading.

Existing node running op-geth v1.101411.x need to run upgrade-pectra.sh in order to upgrade to the latest Pectra release property.

If your node stop syncing after upgrade, the best solution would be to clear everything and resync from scratch with snap sync which takes <24 hours.

Read more: https://docs.optimism.io/notices/pectra-changes#update-to-the-latest-release

Optimistic Ecotone Mainnet Release

Mandatory Upgrade Alert

❗ Mainnet operators are required to update to this release to follow the chain post-Ecotone. This release contains an optimistic Ecotone Mainnet activation time of Mar 14, 00:00:01 UTC.

⚠️ The old release v1.6.1 contained a different Ecotone Mainnet activation date, so it is particularly important for Mainnet operators to upgrade from this release.

For existing node operators

Existing operators upgrading to this release should include OP_NODE__L1_BEACON=<YourBeaconNodeEndpoint> in the .env file before restarting the docker-compose

In case you don't have a beacon node available, you can use QuickNode for the beacon endpoint. For example: https://xxx-xxx-xxx.quiknode.pro/db55a3908ba7e4e5756319ffd71ec270b09a7dce

Changes

1. Bump op-node to version v1.7.1 which is a mandatory upgrade for Ecotone
2. Snap sync support
3. Expose an extra port 39393 for op-geth p2p (Changed from the default port 30303 to prevent conflict with the operator's Ethereum node)
4. Base mainnet and sepolia support

Troubleshooting

Walking back L1Block with curr=0x0000...:0 next=0x0000...:0

If you experience "walking back L1Block with curr=0x0000...:0 next=0x0000...:0" for a long time after the Ecotone upgrade, consider these fixes:

1. Wait for a few minutes. This issue usually resolves itself after some time.
2. Restart docker compose: docker compose down and docker compose up -d --build
3. If it's still not working, try setting OP_GETH__SYNCMODE=full in .env and restart docker compose