LiskHQ/lisk-node v0.4.33 on GitHub

Recommended upgrade

Important

op-node v1.19.11 → v1.20.0, op-reth v2.6.1 → v2.8.0. Upstream marks op-reth v2.8.0 recommended for all operators; op-node v1.20.0 is optional outside GIWA Sepolia. Both are cut from one commit and keep the v1.19.11 / v2.6.1 security fixes (Go 1.26.10, eMudhra distrust). No mainnet env, peer, entrypoint or flag change.

What changes on a Lisk node

op-reth moves from reth v2.5.2 to v2.6.0. The engine persistence threshold default rises from 7 to 50 blocks: more unpersisted blocks stay in memory and are re-executed after an unclean shutdown. Set RETH_ENGINE_PERSISTENCE_THRESHOLD=7 in .env.mainnet to keep the old behaviour. reth's new state masking stays off in op-reth. Upgraded peers negotiate eth/71; older peers still connect at the highest common version.
Storage v1 deprecation: op-reth warns at startup when the datadir uses the Storage v1 layout. Support ends January 2027. To check, stop the node and run op-reth db --chain lisk --datadir <datadir> settings get; storage_v2: false or no settings means v1. Migrate in place with migrate-v2 or restore a v2 snapshot, per the upstream notice. Storage v2 nodes log nothing.
RPC: eth_getLogs with fromBlock past the head returns error -32602 instead of []. Indexers that poll lastSeen + 1 on Lisk's 2 s blocks will hit this.
Block validation: op-reth validates header extraData per fork as op-geth does, and rejects a derived block carrying an invalid transaction at engine_forkchoiceUpdated so op-node replaces it with a deposits-only block, instead of building a block the fault proof rejects.
op-node P2P: the deprecated Req/Resp sync server is removed. The op_node_default_p2p_req_duration_seconds, op_node_default_p2p_req_total and op_node_default_p2p_payload_by_number metrics are gone; drop them from dashboards and alerts. OP_NODE_P2P_SYNC_REQ_RESP is a no-op and was never set here.

Upstream changes inert here

Removed block-access-list flags, historical-proofs v1 storage, --txpool.minimum-priority-fee on local transactions, --rollup.historicalrpc fixes and the kona-node lockstep requirement: this image passes none of those flags and ships op-node. GIWA Sepolia support and the op-node genesis l2 changes don't apply; the superchain-registry bump leaves the Lisk Mainnet config unchanged.

Upgrade

git pull
docker compose up --build --detach

OP Stack Changeset

op-node — v1.20.0 · changelog
op-reth — v2.8.0 · changelog (includes the unpublished v2.7.0)

Full Changelog: v0.4.32...v0.4.33