Releases: LiskHQ/lisk-node
v0.4.15
Essential upgrade for all Lisk Node operators running op-reth
Important
The release includes bug fixes
This release corresponds to:
OP Stack Changeset
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:
OP Stack Changeset
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:
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:
OP Stack Changeset
op-geth
v1.101608.0
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
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
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).
OP Stack Changeset
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
Full Changelog: v0.4.6...v0.4.7
v0.4.6
❗Mandatory upgrade for Lisk Sepolia and Lisk Mainnet nodes (for Jovian Hardfork)❗
Important
- Update your Lisk Sepolia nodes before
Wednesday, 19-Nov-25 16:00:01 UTC (1763568001) - Update your Lisk Mainnet nodes before
Tuesday, 02-Dec-25 16:00:01 UTC (1764691201)- Related OP Governance technical proposal - Ensure your L1 beacon node endpoint can serve all the blobs
Warning
The contained op-node version (v1.101603.5 - Jovian) fixes a bug where nodes doing a historical block sync (from other healthy nodes) would halt when syncing the first block with a user transaction after the Jovian fork.
All Lisk Sepolia and Mainnet node operators must update to this release before the activation timestamp, or their nodes will halt when the corresponding network activates Jovian.
Also, kindly make sure to read through the release notes from Lisk Node v0.4.4 for all other necessary details.
OP Stack Changeset
op-geth
v1.101603.5
Changelog
Full Changelog: v0.4.5...v0.4.6