Skip to content

Releases: base-org/node

v0.9.0

20 Jun 19:07
2dbf4a4
Compare
Choose a tag to compare

Protocol

❗ This is a mandatory release for Base Mainnet node operators. It includes the following protocol upgrade activation:

  • Fjord activates on Mainnet at Wed Jul 10 16:00:01 UTC 2024

✨ RIP-7212, Improved L1 Data Efficiency, Improved L1 Gas Used Calculation and more.

OP Stack Changeset

v0.8.4

28 May 14:31
d3770e1
Compare
Choose a tag to compare

Protocol

❗ This is a mandatory release for Base Sepolia node operators. It includes the following protocol upgrade activation:

  • Fjord activates on Sepolia at Wed May 29 16:00:00 UTC 2024

✨ The Fjord features can be found here.

OP Stack Changeset

v0.8.3

15 May 20:59
e1645a4
Compare
Choose a tag to compare

⬆️ This is a recommended release for node operators. It addresses a security advisory in go-ethereum, see CVE-2024-32972 for more details.

OP Stack Changeset

op-geth
v1.101315.0
Changelog

v0.8.2

03 May 17:23
c0b0349
Compare
Choose a tag to compare

⚠️ This is a highly recommended maintenance release for all node operators It fixes a potential bug in derivation that can lead to a halted node.

OP Stack Changeset

op-node
v1.7.5
Changelog

op-geth
v1.101311.0
Changelog

v0.8.1

13 Mar 02:26
f6c2e9d
Compare
Choose a tag to compare

⬆️ This is a recommended release for node operators using Snap Sync on Base Mainnet & Sepolia. For other users, this is a minor release. Node operators should be on at least v0.8.0.

Changes

  • This release contains a fix to snap sync to ensure that all blocks are inserted to the execution engine when snap sync completes. Previously once snap sync would complete, if blocks where received out of order, the op-node could have internally inconsistent state & the unsafe head could stall for a period of time.
  • This release also contains a safeDB feature which tracks the L1 block L2 blocks are derived from.

v0.8.0

27 Feb 02:56
1ec2d9c
Compare
Choose a tag to compare

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.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.

OP Stack Changeset

v0.7.1

13 Feb 19:48
525775b
Compare
Choose a tag to compare

❗ 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

01 Feb 23:15
397e9cb
Compare
Choose a tag to compare

❗ 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

19 Dec 00:05
2f3557e
Compare
Choose a tag to compare

❗ 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

15 Dec 17:18
2218eab
Compare
Choose a tag to compare

❗ 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.