Skip to content

Releases: ethereum-optimism/op-geth

v1.101503.2 - Isthmus Sepolia

03 Apr 20:41
37be9e0
Compare
Choose a tag to compare

Isthmus Sepolia

Important

This is a required upgrade for any Sepolia Superchain node by Apr 17 as it contains the Isthmus activation on that date. It is a recommended upgrade for all chain operators because it contains an important bug fix of the transaction pool.

This is the Isthmus release for the Sepolia Superchain. It schedules the activation of the Isthmus fork on Thu Apr 17 16:00:00 UTC 2025 (unix timestamp 1744905600).
The following Sepolia chains have the Isthmus upgrade scheduled at this timestamp: base, creator-chain-testnet, ethernity, ink, metal, mode, op, soneium-minato, unichain, zora, lisk. It is mandatory to upgrade nodes for those chains before Apr 17.

🤝 The corresponding mandatory op-node release is v1.13.0.

Chain operators also need to upgrade their batchers to op-batcher/v1.12.0 before activating Isthmus on their chains.

Warning

The activation times for Mode, Metal, and Zora may be delayed in a future release. We will provide an update for those chains in a few days.

Transaction Pool Fixes (#558 #567)

The transaction pool got fixed to properly handle rollup cost (L1 Costs and Operator Fees (Isthmus only)) accounting. This was a longstanding bug that may sometimes have cause transactions to get rejected from the pool even thought the sender had enough balance, or the other way around where transactions could get accepted into the pool but then never get included because the sender's balance was too low.

What's Changed

Full Changelog: v1.101503.1...v1.101503.2

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101503.2

v1.101503.1

14 Mar 16:43
fbc739c
Compare
Choose a tag to compare

This release fixes a regression in serving eth_feeHistory RPC method, and adds snaxchain config.

It is recommended for all users to upgrade.

What's Changed

  • eth: fix OP-Stack fee-history RPC by @protolambda in #543
  • Update superchain-registry@84bce73573f130008d84bae6e924163bab589a11 by @geoknee in #545

Full Changelog: v1.101503.0...v1.101503.1

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101503.1

v1.101503.0 - Pectra L1 readiness

11 Mar 22:05
27ec85a
Compare
Choose a tag to compare

❗ All node operators must upgrade to this op-geth release.

The corresponding op-node release is v1.12.0, see its release nodes for details on a bug that hit Sepolia OP chains when Sepolia activated Pectra.

Upstream go-ethereum update

This release contains all upstream geth changes up to release v1.15.3.

What's Changed

New Contributors

Full Changelog: v1.101500.1...v1.101503.0

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101503.0

v1.101500.1 - Ink Mainnet Holocene Update

24 Feb 20:26
7017b54
Compare
Choose a tag to compare

Ink Mainnet Holocene Update

Ink Mainnet node operators must upgrade to this release before Wed 26 Feb 2025 15:00:00 UTC. This release bumps the Holocene activation time for Ink Mainnet to 1742396400 # Wed 19 Mar 2025 15:00:00 UTC. All other node operators can ignore this release.

🤝 Corresponding op-node release: v1.11.2

What's Changed

Full Changelog: v1.101500.0...v1.101500.1

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101500.1

v1.101500.0 - L1 Pectra Readiness

11 Feb 21:38
9111c8f
Compare
Choose a tag to compare

L1 Pectra Readiness

❗ All node operators must upgrade to this release by the time their chain's L1 activates Pectra.
❗ If you run a full node, don't directly upgrade to this release, but start up once with version v1.101411.8. See its release notes for more details. Archival nodes don't need to follow this upgrade path.

Corresponding op-node release: v1.11.0

This release prepares the OP Stack to handle L1 chains activating Pectra. It includes all changes from the go-ethereum upstream release 1.14.11 and a subset of changes from the 1.15.0 release, all commits on master up to f0e8a3e fix README.md (ethereum/go-ethereum#31076). In particular, support for the new SetCode transaction type 4 is included.

The superchain-registry bindings are also updated to pull in new chain configurations. It is not included as a Go module any more, but instead bundled inside the repo since this release. Downstream dependencies like the Optimism monorepo also use the bundled configurations of op-geth going forward.

What's Changed

New Contributors

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101500.0

Full Changelog: v1.101411.5...v1.101500.0

v1.101411.8 - upgrade path to v1.101500.0

10 Feb 16:59
Compare
Choose a tag to compare

This release contains a fix to the upstream journaling code (b79c44a) to ensure no critical state is lost when upgrading full nodes and the journal is thrown away due to a journal format update. Any full node operator who intends to upgrade their v1.101411.x op-geth node to v1.101500.0 should first restart their node once with this release. When you run this release and shut it down again, search the shutdown logs for a message

Persisting dirty state to disk

and its buffer_layers argument. It should be lower than 128. If that's the case, you can safely go on to upgrade to v1.101500.0.

As steps:

  • You're running v1.101411.x
  • Start up v1.101411.8 once, let it run for a while, shut down.
  • Check shutdown logs for Persisting dirty state to disk message, check that buffer_layers argument is <128
  • You're good to upgrade to v1.101500.0

The background is that updating the upstream geth dependencies between v1.101411.x and v1.101500.0, there were two journal format updates in the underlying geth versions from v1.14.11 to v1.15.0. This causes the journal do be dropped at startup of the new release v1.101500.0. A full node should be able to recover from this, but we suspect a bug in geth (ethereum/go-ethereum#31131) means that more than 128 layers are part of the journal, so when it's thrown away at startup, the node may be missing critical state and needs to heal its state.

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101411.8

Full Changelog: v1.101411.6...v1.101411.8

v1.101411.6 - P2P Fix

30 Jan 13:36
Compare
Choose a tag to compare

❗ All node operators are strongly recommended to upgrade to this release. It contains an urgent security fix (CVE-2025-24883). This fix is the only difference to the prior release v1.101411.5.

Also upgrade your L1 go-ethereum nodes to v1.14.13, which contains the same fix.

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101411.6

Full Changelog: v1.101411.5...v1.101411.6

v1.101411.5

24 Jan 11:28
82acd5a
Compare
Choose a tag to compare

What's Changed

  • Isthmus: re-introduce withdrawals root in block header by @vdamle in #451
  • beacon: add nil check for AccessEvents receiver before invocation by @vdamle in #453
  • go: update SCR dependency to include Soneium Mainnet by @sebastianst in #465

Full Changelog: v1.101411.4...v1.101411.5

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101411.5

v1.101411.4 - Holocene Mainnet Superchain

17 Dec 14:35
efa05b1
Compare
Choose a tag to compare

✨🔴 Holocene Mainnet Superchain Release

This release contains the Holocene activation timestamp for the Mainnet Superchain, on

  • Thu 09 Jan 2025 18:00:01 UTC
  • unix timestamp 1736445601

The corresponding op-node release can be found here.

OP Mainnet Approval

The OP Mainnet Holocene activation is still subject to approval by the governance process on Optimism Upgrade Proposal #11. In the unlike event of a veto by Dec 25, we will publish a new release with the OP Mainnet Holocene activation disabled. The Holocene activation can also be disabled for this release by setting the override flag --override.holocene (or the corresponding env var) to a far-future timestamp, e.g. --override.holocene 2736445601.

Database Rewind panic fix (#446)

This release also contains a fix that again enables op-geth to properly rewind its database in case of a missed Holocene activation and subsequent configuration fix. Without this fix, before attempting to rewind the database to one block before the activation block, a panic would occur:

panic: invalid eip-1559 params in extradata

If you see this after correcting a Holocene timestamp, upgrading to this release should help.

What's Changed

  • core: fix call to post-validation evm message hook by @protolambda in #437
  • op-batcher: exit building loop early if there's not enough DA capacity by @roberto-bayardo in #439
  • chore: fix some problematic function names in comment by @mountcount in #438
  • core: make isForkTimestampIncompatible return false when either fork is post genesis by @geoknee in #447
  • Isthmus: withdrawals root in block header by @protolambda in #383
  • Prepare Holocene mainnet release by @sebastianst in #448
  • Revert "Isthmus: withdrawals root in block header" by @protolambda in #449
  • core: Move blockchain head verification after possible rewind by @sebastianst in #446
  • superchain: update superchain registry dependency by @geoknee in #450

New Contributors

Full Changelog: v1.101411.3...v1.101411.4

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101411.4

v1.101411.3

03 Dec 21:18
717daa1
Compare
Choose a tag to compare

What's Changed

  • miner: fix config unmarshalling by @denis-pingin in #433
  • Update superchain-registry dependency to include Unichain Sepolia holocene_time by @geoknee in #436

New Contributors

Full Changelog: v1.101411.2...v1.101411.3

🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101411.3