Optimism op-supernode v1.0.3 Tightens Hardfork Configuration Checks

Optimism has released opsupernode v1.0.3 as an optional update for operators. The new version adds stricter validation for hardfork activation times in virtualnode rollup configurations. The main change is that the software now rejects configurations where two postgenesis hardforks are set to activate at the same time. It also checks fork ordering from Jovian onward, while forks at or before genesis may still share a timestamp. Optimism said chains already listed in the Superchain registry are not affected. The update is aimed at custom rollup setups, where an invalid fork schedule could otherwise go unnoticed until startup or later chain processing.