Releases: base-org/node
v0.8.0
Protocol
❗ This is a mandatory release for Base Mainnet node operators. It includes the following protocol upgrade activation:
- Ecotone activates on Mainnet at Thu Mar 14 00:00:01 UTC 2024
✨ The Ecotone upgrade brings 4844 and Cancun extensions to the L2.
Config changes
- For Ecotone, op-node needs to connect to an L1 beacon client to be able to fetch blobs. You must specify the endpoint with the
--l1.beaconflag (orOP_NODE_L1_BEACONenv var). - If you are using a Lighthouse CL client, you must update to at least the v4.6.0 finalized release.
OP Stack Changeset
- op-node
- op-geth
v0.7.1
❗ This is a mandatory release for node operators on Sepolia. It includes the following protocol upgrade activation:
- Ecotone activates on Sepolia at Wed Feb 21 17:00:00 UTC 2024
✨ The Ecotone upgrade brings 4844 and Cancun extensions to the L2.
🐛 This release also contains a fix for a tx receipt cache bug which would sometimes result in finalized/safe head stall
Config changes:
With the Ecotone upgrade, op-node needs to connect to an L1 beacon client in order to be able to fetch blobs, whose endpoint is specified with the --l1.beacon flag (or OP_NODE_L1_BEACON env var). If you are using a Lighthouse CL client, you must update to at least the v4.6.0 finalized release.
Versions:
Full changelog:
ethereum-optimism/optimism@v1.5.0...v1.5.1
v0.7.0
❗ This is a mandatory release for node operators on Mainnet and Goerli. It includes two protocol upgrade activations:
- Delta activates on Mainnet at Thu Feb 22 00:00:00 UTC 2024
- Ecotone activates on Goerli at Tue Feb 6 17:00:00 UTC 2024
✨ The Ecotone upgrade brings 4844 and Cancun extensions to the L2.
⚡ Other features in this release include experimental snap sync support for trusted environments and improved shutdown behavior of op-batcher
Config changes:
With the Ecotone upgrade, op-node needs to connect to an L1 beacon client in order to be able to fetch blobs, whose endpoint is specified with the --l1.beacon flag (or OP_NODE_L1_BEACON env var). If you are using a Lighthouse CL client, you must update to at least the v4.6.0 finalized release.
Full changelog:
ethereum-optimism/optimism@v1.4.3...v1.5.0
v0.6.1
❗ This is a recommended release for Base Mainnet. Upgrading to v0.6.0 or higher is required before 2024-01-11 for the Canyon hardfork which activates at Thu Jan 11 17:00:01 UTC 2024 (unix timestamp: 1704992401).
Upgrades op-node/op-batcher/op-proposer from v1.4.0 to v1.4.1.
If you are using custom configuration or entrypoint scripts and haven't already made the changes recommended in release 0.5.0, please ensure you:
- op-node: set the OP_NODE_NETWORK variable, or use the --network flag. The value is one of base-goerli, base-sepolia, base-mainnet.
- op-geth: set the --op-network flag, passing the same network value as above (one of base-goerli, base-sepolia, base-mainnet)
- op-geth: enable the --rollup.superchain-upgrades flag
v0.6.0
❗ This is a mandatory release for Base Mainnet and upgrading is required before 2024-01-10. This includes all features required for the mainnet Canyon hardfork which will be activating at Thu Jan 11 17:00:01 UTC 2024 (unix timestamp: 1704992401).
❗ This is a mandatory release for Base Sepolia & Goerli and upgrading is required before 2023-12-20. This includes all features required for the Delta Network Upgrade which will be activating at 1703116800 Thu Dec 21 00:00:00 UTC 2023 for Goerli & at 1703203200 Fri Dec 22 00:00:00 UTC 2023 for Sepolia.
Upgrades the node software:
Important note: If you are running a batcher or proposer please use the op-batcher/v1.4.1 and op-proposer/v1.4.1 hotfixes.
v0.5.1
Upgraded the node software:
This is an optional release with some non-critical fixes for the base goerli & sepolia Canyon hardfork (primarily: ignoring any P2P blocks that contain withdrawals), as well as setting some suggested flags (see #139):
- op-node:
--rollup.load-protocol-versions=true - op-geth:
--rollup.halt=major - op-geth: removing optional
--rollup.superchain-upgrades
Also adds some quality of life envvars for reducing required disk space (see #146):
- Setting
OP_GETH_GCMODE=fullsupports running afullnode (defaults toarchive) - Setting
OP_GETH_STATE_SCHEME=pathswitches the Ethereum state storage scheme topath(defaults tohash)
v0.5.0
Upgraded the node software:
These releases are Canyon hardfork ready. The configuration and entrypoint scripts have been modified to prepare for the Canyon hardfork on Base Goerli and Base Sepolia testnets at block 1699981200 (Tue Nov 14 17:00:00 2023 UTC).
If you are using custom configuration or entrypoint scripts, please ensure you:
op-node: set theOP_NODE_NETWORKvariable, or use the--networkflag. The value is one ofbase-goerli,base-sepolia,base-mainnet.op-geth: set the--op-networkflag, passing the same network value as above (one ofbase-goerli,base-sepolia,base-mainnet)op-geth: enable the--rollup.superchain-upgradesflag
Verifying your configuration on Goerli & Sepolia
You can verify your node is configured correctly with the following:
- Both op-node and op-geth log their configuration at startup
- Check that Canyon time is set to
1699981200in the op-node logs - Check that Canyon time and Shanghai time are set to
1699981200in the op-geth logs
What's Changed
Full Changelog: v0.4.0...v0.5.0
Contributors
Assets 2
v0.4.0
Adds supervisord which enables support for running both op-geth and op-node in a single container. See https://github.com/base-org/node#running-in-single-container-with-supervisord for more information. Note this is backwards compatible, docker-compose is still supported.
Also upgraded the node software:
v0.3.3
v0.3.2
This release switches the OP_NODE_L2_ENGINE_RPC in the default configuration to use websockets instead of http (see #119). Using the http protocol can cause chain halts in certain scenarios, and this recommends switching to websockets to avoid this. If you configure your OP_NODE_L2_ENGINE_RPC / --l2 differently, we recommend updating your configuration to use ws.
Also upgraded the node software: