op-node v1.19.1

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-reth/v2.3.2 with this release. Prior versions of op-reth will not work with this version of op-node 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).

Note that some chains have a new keep_karst_upgrade_gas boolean field in their superchain registry configuration. Chains with this value set to true are encouraged to manually reset their gas limit after Karst activates on Sepolia and Mainnet. See the notice page for more information.

What's Changed in op-node/v1.19.1

• superchain: load keep_karst_upgrade_gas from registry into op-node by @geoknee in #21566
• derive: fix sticky upgrade gas for Karst (but keep it for select chains) by @sebastianst in #21441
• Activate Osaka at Karst and add engine getPayloadV5 by @sebastianst in #21337
• op-node: default --l2.enginekind to reth by @sbvegan in #21295

Full Changelog: op-node/v1.19.0...op-node/v1.19.1

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