Optimism has issued two targeted software updates for its OP Stack infrastructure, focusing on sequencer efficiency and configuration safety. The releases, both dated October 1, prepare operators for the upcoming Glamsterdam hardfork while reducing the risk of operational hiccups on Layer 2 networks.

Sequencer Performance Improvements in op-node v1.19.8

Optimism recommends that sequencer operators upgrade to op-node version 1.19.8, especially those running with the --l2.follow.source setting. The update addresses recurring slowdowns in block production that occurred during transitions to a new Layer 1 origin.

Under the previous approach, sequencers sometimes experienced delays when required Ethereum block data and receipts had not yet been fetched through local derivation. The new version prefetches each newly observed Layer 1 head block and its receipts as soon as the head appears. If the prefetch operation fails, the node logs a warning and reverts to the standard fetch path. This change aims to minimize avoidable latency in the component responsible for ordering Layer 2 transactions.

The release also strengthens validation of hardfork activation schedules in custom rollup configurations. The software now refuses to start if a configuration sets Jovian or any later hardfork to activate at the same post-genesis timestamp as the preceding fork, or if later forks appear out of sequence. Chains already listed in the Superchain registry remain unaffected by these checks.

Stricter Hardfork Validation in op-supernode v1.0.3

In parallel, Optimism published op-supernode version 1.0.3 as an optional update for operators. This release applies tighter validation rules to virtual-node rollup configurations. It rejects any setup that activates two hardforks at the same timestamp after genesis, beginning with Jovian, and verifies that subsequent forks maintain correct ordering.

Hardforks scheduled at or before genesis may still share a timestamp. As with the op-node changes, networks already included in the Superchain registry are not impacted. The new checks primarily target custom configurations that might otherwise load an invalid upgrade sequence.

These safeguards become increasingly relevant as the OP Stack supports a growing number of independent chains. Each additional configuration option expands the potential for human error, and early detection at startup helps prevent inconsistencies across network components.

Sepolia Deadline for Glamsterdam Hardfork

Operators running OP Stack chains on the Sepolia testnet face a firm deadline. They must upgrade to at least op-node version 1.19.5 before the Glamsterdam hardfork activates on October 6. Version 1.19.8 is not mandatory for every operator, but the minimum requirement ensures compatibility with the scheduled network upgrade.

End users of Optimism-based applications need take no action. The updates concern infrastructure teams responsible for sequencers, nodes, and custom deployments. Maintaining alignment across the expanding OP Stack components remains essential for reliable Layer 2 performance as the network continues to evolve alongside Ethereum.