Deep Dive
1. Node Upgrade for OP-Reth Client (23 July 2025)
Overview: This update is a recommended upgrade for node operators running the op-reth execution client. It ensures nodes stay compatible with the latest optimizations and fixes from the OP Stack, which Lisk's Layer 2 is built upon.
The release, tagged v0.3.7, is part of Lisk's ongoing maintenance of its node software following its migration to become an Optimism Superchain Layer 2. These routine upgrades incorporate upstream changes from the OP Stack's op-reth component, which handles transaction execution and state management.
What this means: This is neutral for Lisk because it represents standard maintenance. For users, it means the network remains stable and up-to-date with core infrastructure improvements, though it doesn't introduce new features directly visible to end-users.
(LiskHQ)
2. Mandatory Mainnet Upgrade for Hardfork (23 April 2025)
Overview: This was a critical, mandatory upgrade (v0.2.10) for all Lisk Mainnet node operators. It prepared the network for the activation of a scheduled hardfork, ensuring a smooth transition and continued network security.
The release contained necessary changes from the OP Stack (op-node, op-geth, op-reth) to implement the "Isthmus" hardfork. Node operators were required to upgrade before the May 9, 2025 deadline to avoid disruption.
What this means: This was bullish for Lisk because successful hardforks demonstrate active development and network maturity. For users, it meant the underlying blockchain became more robust and capable, supporting the long-term health of the ecosystem.
(LiskHQ)
3. Final SDK Release Before Archive (15 March 2024)
Overview: Version 6.0.2 was the final release of the Lisk SDK before its repository was archived. It primarily fixed bugs and improved data storage within the Chain Connector plugin, which is crucial for nodes that relay information between chains.
This update marked the end of active development on Lisk's original proprietary blockchain framework, as the project pivoted to its current Ethereum Layer 2 architecture.
What this means: This is neutral for Lisk, reflecting a concluded chapter. It provided final stability improvements for the old network but signaled the strategic shift to building on Ethereum. For developers, it means the old SDK is no longer actively developed.
(LiskArchive)
Conclusion
Lisk's codebase activity has transitioned from maintaining its independent SDK to regularly updating its OP Stack-based node software, reinforcing its new identity as a committed Ethereum Layer 2. The latest updates are operational, ensuring network reliability and forward compatibility rather than introducing flashy new features. How will the focus on core infrastructure support the growth of its targeted ecosystems in emerging markets?