Optimism op-supernode v1.0.3 Adds Stricter Hardfork Configuration Checks

Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure TL;DR Optimism has released op-supernode v1.0.3 as an optional operator update. The release tightens validation around hardfork activation times and rejects invalid post-genesis fork ordering in custom rollup configs. Existing chains in the Superchain registry are not affected by the configuration issue described in the release notes. Optimism’s latest supernode release is a small update with a very specific purpose: stop bad hardfork schedules from being loaded in the first place. op-supernode v1.0.3 was published October 1 as an optional release for operators. It adds stricter validation of hardfork activation times in virtual-node rollup configurations. There is no new indexing engine, state-sync overhaul or memory-leak fix in the official notes. The change is about configuration correctness. Two post-genesis forks cannot share the same activation time Under the new checks, op-supernode refuses to load a virtual node configuration that activates two hardforks at the same timestamp after genesis. The rule applies from Jovian onward, and every later fork is checked for correct order...