Overview
Note
This is an optional release for op-supernode operators. It contains stricter validation of hardfork activation times in rollup configs.
Other changes
Configuration
- op-supernode now refuses to load a virtual node's rollup config that activates two hardforks at the same timestamp after genesis. The check applies to Jovian and every later fork, and every fork is now checked for correct activation order. Forks that activate at or before genesis may still share a timestamp. Existing chains in the superchain registry are unaffected. A custom config that schedules, say, Karst and another later fork at the same post-genesis timestamp must be corrected before upgrading (#22838)
Full Changelog: op-supernode/v1.0.2...op-supernode/v1.0.3
🚢 Docker Image: