v0.4.16

Required upgrade for all Lisk Node operators

Important

The release includes upstream security fixes (go-ethereum v1.17.0/v1.17.1), important bug fixes, a major op-reth version bump, and a breaking default change in op-node.
This release corresponds to:

• https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.16.13
• https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101702.1
• https://github.com/ethereum-optimism/optimism/releases/tag/op-reth/v2.1.0

Warning

Action required for operators relying on Req/Resp CL P2P sync. Starting in op-node/v1.16.12, the --syncmode.req-resp flag defaults to false. If you rely on Req/Resp sync, set it to true explicitly and ensure you have a healthy EL p2p network.

Caution

op-geth is being deprecated. Optimism has announced the deprecation of op-geth as an OP Stack execution client. Operators currently running op-geth should plan a migration to op-reth. See the upstream notice for the timeline and migration guidance: https://docs.optimism.io/notices/op-geth-deprecation

Highlights

• op-geth includes upstream security fixes. op-geth/v1.101701.0 is marked essential for all chains by upstream — it merges go-ethereum v1.17.0 and v1.17.1 security patches. op-geth/v1.101702.1 then merges go-ethereum v1.17.2, which includes a fix for a debug_executionWitness issue that could corrupt node data, plus history pruning improvements, RPC hardening, and trie/state correctness fixes. Default cache size is now 4 GB.
• op-reth bumps to a major new version via op-reth/v2.0.0 → v2.1.0. v2.0.0 ports the underlying reth 2.0 changes into op-reth and integrates op-revm into the workspace (marked as a breaking change in upstream commits). v2.1.0 activates EIP-7823 (modexp upper bounds) on the Karst fork, fixes the proofs ExEx wait before debug_executePayload, and includes interim fixes from v1.11.5 (proofs-exex correctness, drop interop txs after reorg).
• op-node spans v1.16.9–v1.16.13. Highlights from this range:
  • Security: bundles the op-geth security fixes flagged in op-node/v1.16.9.
  • Derivation pipeline hardening: drop bad channel decompression as NotEnoughData, drop malformed span batch tx data as NotEnoughData, SetCodeTxType check in span batch validation, SafeDB use-after-Close guard.
  • Performance: batch safe-head FCU calls to one per derived L1 block.
  • Breaking default: --syncmode.req-resp now defaults to false (see Action required above).

OP Stack Changeset

op-node
v1.16.13
Changelog

op-geth
v1.101702.1
Changelog

op-reth
v2.1.0
Changelog

Full Changelog: v0.4.15...v0.4.16

v0.4.15

Essential upgrade for all Lisk Node operators running op-reth

Important

The release includes bug fixes
This release corresponds to:

• https://github.com/ethereum-optimism/optimism/releases/tag/op-reth/v1.11.3

OP Stack Changeset

op-reth
v1.11.3
Changelog

Full Changelog: v0.4.14...v0.4.15

v0.4.14

Essential upgrade for all Lisk Node operators

Important

The release includes security fixes
This release corresponds to:

• https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.16.8
• https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101609.2

OP Stack Changeset

op-node
v1.16.8
Changelog

op-geth
v1.101609.2
Changelog

Full Changelog: v0.4.13...v0.4.14

v0.4.13

Essential upgrade for all Lisk Node operators

Important

The release includes security fixes
This release corresponds to:

• https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101609.0
• https://github.com/ethereum-optimism/optimism/releases/tag/op-reth%2Fv1.11.0

OP Stack Changeset

op-geth
v1.101609.0
Changelog

op-reth
v1.11.0
Changelog --- op-reth now in https://github.com/ethereum-optimism as of v1.11.0 per https://x.com/Optimism/status/2019093628841590965

Full Changelog: v0.4.12...v0.4.13

v0.4.12

Essential upgrade for all Lisk Node operators

Important

This release corresponds to:

• https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.16.6
• https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101608.0
• https://github.com/paradigmxyz/reth/releases/tag/v1.10.2

OP Stack Changeset

op-node
v1.16.6
Changelog

op-geth
v1.101608.0
Changelog

op-reth
v1.10.2
Changelog

Full Changelog: v0.4.11...v0.4.12

v0.4.11

Optional upgrade for all Lisk Node operators running op-reth client

Note

This release corresponds to https://github.com/paradigmxyz/reth/releases/tag/v1.9.4
This also includes an update to the static peer for mainnet

OP Stack Changeset

op-reth v1.9.4
Changelog

Full Changelog: v0.4.10...v0.4.11

v0.4.10

Essential upgrade for all Lisk node operators

Warning

This release includes security fixes and corresponds to the following:
https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.16.5
https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101605.0

Full Changelog: v0.4.9...v0.4.10

v0.4.9

Essential upgrade for all Lisk node operators

Note

Includes everything in the v0.4.8 release (the update to op-node 1.16.3) plus modifies op-node-lisk-sepolia.patch to apply properly in the lisk sepolia builds of op-node

Full Changelog: v0.4.8...v0.4.9

v0.4.8

Essential upgrade for all Lisk node operators use v0.4.9 instead of v0.4.8

Note

To quote the Optimism release:

This release contains an important fix of the blob fetching logic to handle the case where multiple blobs with the same content (but different indices in the block) are requested. Without this fix, a safe head stall is possible, due to an error triggered if the batcher submits multiple blobs with the same content (ethereum-optimism/optimism#18492).

more details here

OP Stack Changeset

op-node
v1.16.3
Changelog

Full Changelog: v0.4.7...v0.4.8

v0.4.7

Recommended upgrade for all Lisk Sepolia node operators running op-reth client

Note

We recommend all the Lisk Sepolia node operators running op-reth clients to upgrade as Jovian activates today: Wed 19 Nov 2025 16:00:01 UTC

OP Stack Changeset

op-reth v1.9.3
Changelog

Full Changelog: v0.4.6...v0.4.7