Lisk Mainnet snap-sync peer update
Important
Mainnet operators running snap sync must update OP_RETH_TRUSTED_PEERS. The trusted-peer node keys were rotated after an infrastructure maintenance operation; the old node IDs no longer match the running peers, so an op-reth still configured with them will fail the P2P handshake. Endpoints are unchanged (34.147.89.221:30303/30304/30403/30404) — only the keys rotated.
Note
Nodes in the default full-sync mode are unaffected: the snap-sync block in .env.mainnet is commented out. No client bumps (op-node v1.19.4, op-reth v2.4.2) and no image, entrypoint, or README change. OP_RETH_BOOTNODES and Lisk Sepolia are unchanged.
Highlights
.env.mainnet — four new node keys in the commented OP_RETH_TRUSTED_PEERS snap-sync example; IPs and ports unchanged. Consumed by op-reth as --trusted-peers.
Upgrade
Full-sync operators: nothing to do.
Snap-sync operators — your uncommented OP_RETH_TRUSTED_PEERS is a local edit, so git pull will not replace it. Replace it with the new value:
OP_RETH_TRUSTED_PEERS=enode://401c9dd2da9a7809758902abce81030f29ba42660c5ef230dafc87d76a285a62ffa70ab0f74c640ad9ddc7b2b9981cbb85efc70a6a30d7d797aa75af21527203@34.147.89.221:30303,enode://7c311e116a5d8b74fb6630b905036baaf72d58986d39880814083f5d118a2be19948f0afee8452be6093ff45cb057479fae2812964f7d4090671c5c78cb071be@34.147.89.221:30304,enode://7d5dfe8e4496a071bab995bea2f136fc21747eea5dff49ea3deff08f08e219807fc4081e8396f56c404009937ef6621e61e116f1c9c2aa0baa82b722047abc0b@34.147.89.221:30403,enode://63cac6eb1ff78ad9c7a1dbcddb831fd58562f85e8d7c438db0e2afcfce00f0a46df4aba2fbfc9b194f405d0d42dd7d25c2e690acde87842b5530e1707b88d7f2@34.147.89.221:30404Then restart:
git pull
docker compose up --detachOP Stack Changeset
op-node — unchanged, v1.19.4
op-reth — unchanged, v2.4.2
Full Changelog: v0.4.25...v0.4.26