ethereum-optimism/optimism op-supernode/v1.1.0

op-supernode v1.1.0

on GitHub

Overview

Chain Configuration

• GIWA Sepolia added to the embedded superchain registry (#23511). A virtual node can now be configured for GIWA Sepolia (chain ID 91342) by name with --vn.91342.network=giwa-sepolia instead of an explicit rollup config. Every fork through Karst is already active on GIWA Sepolia, so this adds no new activation, and a supernode on an earlier release keeps following GIWA Sepolia with an explicit --vn.91342.rollup.config. The OP Labs devnet sepolia-devnet-3-sepolia-devnet-3 is added as well. No other chain's activation times or rollup parameters change.

Other changes

P2P

• Virtual nodes no longer serve the Req/Resp P2P sync protocol (payloads by number) to peers. op-node stopped making these requests in op-node/v1.19.1, so only peers on op-node/v1.19.0 or earlier lose a source of missing payloads. --vn.all.p2p.sync.req-resp and --vn.<chainID>.p2p.sync.req-resp (OP_SUPERNODE_VN_ALL_P2P_SYNC_REQ_RESP, OP_SUPERNODE_VN_<chainID>_P2P_SYNC_REQ_RESP) are still accepted but have no effect, so existing configurations start unchanged; they can be removed. The op_node_supernode_p2p_req_total, op_node_supernode_p2p_req_duration_seconds and op_node_supernode_p2p_payload_by_number metrics, which only counted served requests, are no longer exported, so remove them from any dashboards and alerts (#21499)

Security

• The Go 1.26.10 toolchain and the CA trust store without the compromised eMudhra roots (CVE-2026-111943) already shipped in op-supernode/v1.0.6 and are unchanged in this release (#23546, #23566)

Full Changelog: op-supernode/v1.0.6...op-supernode/v1.1.0

🚢 Docker Image:

• https://us-docker.pkg.dev/oplabs-tools-artifacts/images/op-supernode:v1.1.0