TL;DR
- Optimism has released op-node v1.19.8 and recommends it particularly for sequencer operators using `–l2.follow.source`.
- The release fixes recurring slow block builds around L1-origin transitions and strengthens validation of hardfork activation ordering.
- Sepolia OP Stack operators must be on op-node v1.19.5 or later before the October 6 Glamsterdam hardfork.
Optimism has shipped a focused op-node update aimed at keeping sequencers fast and configuration mistakes from turning into upgrade problems.
Version 1.19.8 was released October 1 and is recommended particularly for sequencer operators running with `–l2.follow.source`.
This is not a user-facing OP token event. It is the kind of infrastructure release that matters precisely because most users should never notice it.
The release targets slow blocks at L1-origin transitions
Optimism says sequencers will now prefetch each new L1 head’s block and receipts as soon as the head is observed.
Previously, operators using the follow-source configuration could hit recurring slow block builds when the L1 origin changed and the required data had not already been fetched through local derivation.
The new behavior moves that work earlier. If the prefetch fails, op-node logs a warning and falls back to the normal fetch path.
That is a narrow change with an obvious operational benefit: fewer avoidable delays in the component responsible for ordering Layer 2 transactions.
The wider OP Stack maintenance cycle already includes the recent required op-batcher v1.17.0 release and the rollout of Superchain interoperability on Sepolia.
Hardfork configs get stricter checks
The second major change is defensive.
op-node now refuses to start when a custom rollup configuration activates Jovian or a later hardfork at the same post-genesis timestamp as the preceding fork, or when later forks are scheduled out of order.
Optimism says chains already included in the Superchain registry are not affected. The checks matter mainly for custom configurations that could otherwise encode an invalid upgrade sequence.
That becomes more relevant as the OP Stack accumulates more named network upgrades and more independent chains use the software.
Bitcoinist has also covered Upgrade Proposal 20 and Super Root dispute games, part of the same trend toward a more complex multi-chain fault-proof environment.
Sepolia operators have a deadline
The release notes also warn operators on Sepolia OP Stack chains that they must run op-node v1.19.5 or newer before the Glamsterdam hardfork on October 6.
That requirement is separate from whether every operator needs v1.19.8 specifically.
For ordinary users, there is no wallet migration or action to take. For sequencer and node teams, the release is another reminder that Layer 2 reliability depends on keeping a growing stack of infrastructure components aligned with Ethereum and with each other.
—
This article was written by the News Desk and edited by Samuel Rae.
