Overview
Note
This is an optional release for all op-supernode operators. It removes op-node's sequencer.max-safe-lag option from the virtual nodes, and updates golang.org/x/net past two advisories that do not affect op-supernode.
Breaking changes
- Virtual-node
sequencer.max-safe-lagflags removed (#23738). Sequencing no longer pauses when the unsafe head runs ahead of the safe head. Remove--vn.all.sequencer.max-safe-lagand--vn.<chainID>.sequencer.max-safe-lagfrom the launch configuration before upgrading, because op-supernode rejects them as unknown flags. TheOP_SUPERNODE_VN_ALL_SEQUENCER_MAX_SAFE_LAGandOP_SUPERNODE_VN_<chainID>_SEQUENCER_MAX_SAFE_LAGenvironment variables are no longer read. The option was disabled by default, so a supernode that never set it is unaffected.
Other changes
- Update
golang.org/x/netto v0.62.0, which fixes CVE-2026-78661 and CVE-2026-97045 (#23728). Both are in the module'shtmlpackage, which op-supernode does not use, so earlier releases were not affected; the update clears vulnerability-scanner findings against the module.
Full Changelog: op-supernode/v1.1.0...op-supernode/v1.1.1
🚢 Docker Image: