TL;DR
Optimism has launched op-node v1.19.8 and recommends it significantly for sequencer operators utilizing `–l2.comply with.supply`.
The discharge fixes recurring sluggish block builds round L1-origin transitions and strengthens validation of hardfork activation ordering.
Sepolia OP Stack operators should be on op-node v1.19.5 or later earlier than the October 6 Glamsterdam hardfork.
Optimism has shipped a centered op-node replace aimed toward retaining sequencers quick and configuration errors from turning into improve issues.
Model 1.19.8 was launched October 1 and is beneficial significantly for sequencer operators working with `–l2.comply with.supply`.
This isn’t a user-facing OP token occasion. It’s the form of infrastructure launch that issues exactly as a result of most customers ought to by no means discover it.
The discharge targets sluggish blocks at L1-origin transitions
Optimism says sequencers will now prefetch every new L1 head’s block and receipts as quickly as the pinnacle is noticed.
Beforehand, operators utilizing the follow-source configuration might hit recurring sluggish block builds when the L1 origin modified and the required knowledge had not already been fetched by way of native derivation.
The brand new conduct strikes that work earlier. If the prefetch fails, op-node logs a warning and falls again to the conventional fetch path.
That could be a slender change with an apparent operational profit: fewer avoidable delays within the element accountable for ordering Layer 2 transactions.
The broader OP Stack upkeep cycle already consists of the latest required op-batcher v1.17.0 launch and the rollout of Superchain interoperability on Sepolia.
Hardfork configs get stricter checks
The second main change is defensive.
op-node now refuses to begin when a customized rollup configuration prompts Jovian or a later hardfork on the similar post-genesis timestamp because the previous fork, or when later forks are scheduled out of order.
Optimism says chains already included within the Superchain registry aren’t affected. The checks matter primarily for customized configurations that might in any other case encode an invalid improve sequence.
That turns into extra related because the OP Stack accumulates extra named community upgrades and extra unbiased chains use the software program.
Bitcoinist has additionally coated Improve Proposal 20 and Tremendous Root dispute video games, a part of the identical pattern towards a extra advanced multi-chain fault-proof surroundings.
Sepolia operators have a deadline
The discharge notes additionally warn operators on Sepolia OP Stack chains that they have to run op-node v1.19.5 or newer earlier than the Glamsterdam hardfork on October 6.
That requirement is separate from whether or not each operator wants v1.19.8 particularly.
For extraordinary customers, there isn’t any pockets migration or motion to take. For sequencer and node groups, the discharge is one other reminder that Layer 2 reliability depends upon retaining a rising stack of infrastructure elements aligned with Ethereum and with one another.
—
This text was written by the Information Desk and edited by Samuel Rae.
Editorial Course of for bitcoinist is centered on delivering totally researched, correct, and unbiased content material. We uphold strict sourcing requirements, and every web page undergoes diligent evaluation by our group of high know-how specialists and seasoned editors. This course of ensures the integrity, relevance, and worth of our content material for our readers.
