[!Warning] This is a mandatory release for all node operators. It includes the Mainnet timestamps for the Karst hardfork. The following Mainnet chains will activate on 1783526401 (Wed Jul 8 2026 16:00:01 UTC), pending governance approval: op, ink, zora, mode, lisk, metal, unichain, soneium, ethernity, tbn Reminder: op-geth has reached end of support, so you must be running op-reth to support the karst activation. For more details on this network upgrade see our notice page.
[!IMPORTANT]
Operators must use op-node/v1.19.1 with this release. Prior versions of op-node will not work with this version of op-reth after Karst due to a new engine API method (getPayloadV5) used after Karst. See the notice page for more details about recommended versions (including flashblocks components).
op-reth can now load OP Sepolia and OP Mainnet timestamps from the superchain registry. If you are a node operator for either of those chains, you do not need to specify a custom genesis file with the --chain flag.[!CAUTION] Mandatory upgrade. Fixes eth_estimateGas after the Karst hardfork.View full release on GitHub →
Please use op-reth v2.3.3 instead. It contains a bug fix for eth_estimateGas.
[!Warning] This is a mandatory release for all node operators. It includes the Mainnet timestamps for the Karst hardfork. The following Mainnet chains will activate on 1783526401 (Wed Jul 8 2026 16:00:01 UTC), pending governance approval: op, ink, zora, mode, lisk, metal, unichain, soneium, ethernity, tbn Reminder: op-geth has reached end of support, so you must be running op-reth to support the karst activation. For more details on this network upgrade see our notice page.
[!IMPORTANT]
Operators must use op-node/v1.19.1 with this release. Prior versions of op-node will not work with this version of op-reth after Karst due to a new engine API method (getPayloadV5) used after Karst. See the notice page for more details about recommended versions (including flashblocks components).
op-reth can now load OP Sepolia and OP Mainnet timestamps from the superchain registry. If you are a node operator for either of those chains, you do not need to specify a custom genesis file with the --chain flag.Update: we are aware of an issue impacting calls to eth_estimateGas after Karst has activated. We have a fix that will be released in op-reth/v2.3.3 prior to mainnet activation. The notice page has more details.View full release on GitHub →[!IMPORTANT] This release fixes a deadlock bug that would cause a node to stall, and supersedes the v2.2.5 and v2.3.0 releases.
[!WARNING] This is a mandatory release for all node operators. It includes Sepolia and Mainnet timestamps for the Karst hardfork. Operators must upgrade before the scheduled hard fork times. The following Sepolia chains will activate onOP Sepolia:1781712001(Wed Jun 17 2026 16:00:01 UTC): op, ink, zora, mode, lisk, metal, unichain, soneium-minato, ethernity, creator-chain-testnet The following Mainnet chains will optimistically activate on1783526401(Wed Jul 8 2026 16:00:01 UTC), pending governance approval: op, ink, zora, mode, lisk, metal, unichain, soneium, ethernity, tbn Reminder: op-geth has reached end of support, so you must be running op-reth to support the karst activation. For more details on this network upgrade see our notice page.
- Due to a bug in op-reth, the Karst activation timestamp is not loaded from the Superchain Registry for
op-sepoliaandop. You must configure it manually by providing a genesis file passed via--chain. Download the pre-built genesis file and pass it directly — do not edit the file. - Download genesis.json.
- The genesis file must not include an
osakaTimefield. The pre-built file linked above is compatible withop-reth v2.3.1as-is. Both the SCR loading bug and this restriction will be fixed in a following op-reth release so this won’t be necessary for OP Mainnet.
[!IMPORTANT]
This release contains support for historical proofs storage format v2. It can be enabled by setting --proofs-history.storage-version=v2. Note that the proofs data has to be reinitialized if switching to the new storage version format. See the docs for further details.
View full release on GitHub →This is a bug fix release of op-reth.View full release on GitHub →
[!CAUTION] Recomended upgrade for operators running op-reth v2.0.0 and above with historical proofs activated This upgrade fixes some errors in op-reth for historical proofs computation and bumps reth to v2.2.0.View full release on GitHub →
This release includes bug fixes, updates to NUT bundle types, and removes deprecated ProtocolVersions support.This version includes Superchain Registry updates for Worldchain and is a required update for that networkView full release on GitHub →
[!IMPORTANT] This is a strongly recommended release as it bumps the underlying reth dependency to its official 2.0.0 release.View full release on GitHub →
Description
This release ports most of the changes fromreth 2.0 into op-reth. It also ports op-revm to ethereum-optimism/optimism, completing the migration of the op-variants of paradigm/tempo crates to ethereum-optimism/optimism.View full release on GitHub →What’s Changed in op-reth/v1.11.5
- fix(proofs-exex): error if state unavailable instead of falling back to historical provider by @dhyaniarun1993 in #19855
- fix(op-alloy): resolve
NetworkWalletconflict with alloy 1.8 by @suchapalaver in #19756 - feat(op-reth): Drop interop transactions after reorg by @wwared in #19814
[!WARNING] This is an essential bug fix release for all chains. See the upstream release notes (https://github.com/paradigmxyz/reth/releases/tag/v1.11.1, https://github.com/paradigmxyz/reth/releases/tag/v1.11.2 and https://github.com/paradigmxyz/reth/releases/tag/v1.11.3) for guidance regarding backwards compatibility.View full release on GitHub →
Description
Firstop-reth release from the optimism monorepo.Major changes:- Imports historical proofs generation tooling to
op-reth