❗This is a mandatory release for Base Mainnet nodes. It contains required upgrades for clients to operate with the Granite hard fork for Base Mainnet on Sep 11, 2024 16:00:01 UTC.

Changeset

op-node
v1.9.1
Changelog

op-geth
v1.101408.0
Changelog

op-reth
v1.0.6
Changelog

❗This is a mandatory release for Base Sepolia nodes running Reth

This release contains upgrades for Reth clients operate with Granite hard fork for Base Sepolia Testnet on Mon Aug 12 16:00:00 UTC 2024. Geth client changes were included in v0.10.0

Changeset
op-node
v1.9.0
Changelog

op-reth
v1.0.5
Changelog

❗This is a mandatory release for Base Sepolia nodes

It contains the activation of the Granite hardfork on the Sepolia network on Mon Aug 12 16:00:00 UTC 2024.
Node operators of Base Sepolia nodes must update to this release before this activation timestamp, or their nodes will halt when the network activates Granite. It is a recommended update for mainnet nodes as it contains various improvements and bug fixes.

Note: This release contains Geth changes for Granite only. Reth compatibility for the Granite hard fork will be included in a future release.

OP Stack Changeset
op-node
v1.9.0
Changelog

op-geth
v1.101315.3
Changelog

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

• op-node
  • v1.7.7
  • Changelog
• op-geth
  • v1.101315.2
  • Changelog

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

• op-node
  • v1.7.6
  • Changelog
• op-geth
  • v1.101315.1
  • Changelog

⬆️ 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

⚠️ 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

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

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

• op-node
  • v1.7.0
  • Changelog
• op-geth
  • v1.101308.2
  • Changelog

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

• op-node v1.5.1
• op-geth v1.101308.0

Full changelog:
https://github.com/ethereum-optimism/optimism/compare/v1.5.0...v1.5.1

❗ 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:
https://github.com/ethereum-optimism/optimism/compare/v1.4.3...v1.5.0

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

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

This version also includes mainnet Canyon; however we recommend running https://github.com/base-org/node/releases/tag/v0.5.1 on mainnet.

Upgrades the node software:

• op-node v1.4.0
• op-geth v1.101304.2

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.

Upgraded the node software:

• op-node v1.3.1
• op-geth v1.101304.1

This is an optional release with some non-critical fixes for the 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=full supports running a full node (defaults to archive)
• Setting OP_GETH_STATE_SCHEME=path switches the Ethereum state storage scheme to path (defaults to hash)

Upgraded the node software:

• op-node v1.3.0
• op-geth v1.101304.0

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

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 1699981200 in the op-node logs
• Check that Canyon time and Shanghai time are set to 1699981200 in the op-geth logs

What's Changed

• Update op-geth + op-node in preparation for the canyon hardfork by @mdehoog in https://github.com/base-org/node/pull/135

Full Changelog: https://github.com/base-org/node/compare/v0.4.0...v0.5.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:

• op-node v1.2.0
• op-geth v1.101301.1

Fixes a bug in v0.3.2 for those using docker-compose: the cmd was set to sh which doesn't support the variable substitution introduced in #119. Switches to bash.

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:

• op-node v1.1.4

This release contains the Base sepolia configuration.

Also upgraded the node software:

• op-node v1.1.3
• op-geth v1.101200.1

Update op-node from v1.1.1 to v1.1.3