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.
What's Changed in op-reth/v2.3.2
- rust: centralize OP fork → implied L1 fork mapping by @sebastianst in #21368
- feat(op-reth/txpool): impl ValidatingPool for OpPool by @einar-oplabs in #21378
- alloy-op-evm: reject user txs in fork-activation blocks (forks ≥ Jovian) by @sebastianst in #21326
- rust: update reth to v2.3.0 by @sebastianst in #21348
- feat(op-reth): add configurable max uncompressed block size cap by @joshklop in #21353
- Activate Osaka at Karst and add engine getPayloadV5 by @sebastianst in #21337
- feat: add op pool public api [@julio4 community pr] by @einar-oplabs in #21305
Full Changelog: op-reth/v2.3.1...op-reth/v2.3.2
🚢 Docker Image: https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-reth:v2.3.2