op-node, op-batcher, op-proposer v1.7.0 - Optimistic Ecotone Mainnet Release
✨🔴 Optimistic Ecotone Mainnet Release
❗ 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.
v1.6.1 contained a different Ecotone Mainnet activation date, so it is particularly important for Mainnet operators to upgrade from this release.
Optimism Governance Voting Cycle 19
The Ecotone activation contained in this release is still subject to approval during the currently ongoing Optimism Governance voting cycle 19, see the Governance Proposal of the Ecotone Protocol Upgrade. The voting period ends on Mar 6 while the veto period ends on Mar 13, 19:00 UTC.
We will soon publish a Veto Release in advance with the Ecotone OP Mainnet activation removed so node operators can prepare for the unlikely event of a negative vote or a veto. We will also soon provide documentation on how to override the Ecotone activation included in this or future releases via command line flags or env vars. This leaves an emergency window of 5h to change the node configuration, or update to the Veto Release, in the unlikely event that the veto period ends in a veto.
New Beacon Endpoint
Node operators need to configure a Beacon endpoint for op-node, because soon after the Ecotone activation, batch transactions will be sent as 4844 blobs, and blobs can only be retrieved from Beacon nodes. If you're using Lighthouse, make sure to use at least version v5.0.0, which contains the Dencun upgrade for Mainnet.
The op-node provides a new command line flag & env var for configuring the Beacon endpoint: --l1.beacon and $OP_NODE_L1_BEACON. If you need to configure an HTTP header for authentication with the Beacon endpoint, you can use the flag --l1.beacon-header or $OP_NODE_L1_BEACON_HEADER.
❗ We encourage all node operators to already configure their Beacon endpoint to avoid interruptions after the Ecotone activation.
Experimental Snap Sync (execution-layer sync)
op-node 1.7.0 and op-geth v1.101308.2 now support Snap Sync. To enable snap sync set the --syncmode=execution-layer flag on op-node. op-geth should also be set to --syncmode=snap and must have discovery and be peered to the network for snap sync to work.
This feature is ready to be tested, but still may contain some bugs as it is rolled out.
Partial Changelog (affecting op-node)
- op-node: Expose method to load rollup config without a CLI context by @ajsutton in #9554
- op-service/client: Add http header option to BasicHTTPClient by @sebastianst in #9601
- op-node: Add optional Beacon header flag by @sebastianst in #9604
- op-node: Unhide syncmode flag by @trianglesphere in #9611
- op-node: Fix bootnodes port by @trianglesphere in #9621
- Import
SystemConfigProxyaddress from new location insuperchain(registry). by @geoknee in #9585 - Update Ecotone mainnet activation to Mar 14 00:00:01 UTC by @sebastianst in #9625
- op-node: Add flag categories by @trianglesphere in #9629
Full Changelog (monorepo): v1.6.1...v1.7.0
🚢 Docker Images
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.0
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-batcher:v1.7.0
https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-proposer:v1.7.0
