Optimism Recommends op-node v1.19.8 For Sequencers Ahead Of Glamsterdam
TL;DR
- Optimism has launched op-node v1.19.8 and recommends it notably for sequencer operators utilizing `–l2.comply with.supply`.
- The launch fixes recurring sluggish block builds round L1-origin transitions and strengthens validation of hardfork activation ordering.
- Sepolia OP Stack operators have to be on op-node v1.19.5 or later earlier than the October 6 Glamsterdam hardfork.
Optimism has shipped a targeted op-node replace geared toward maintaining sequencers quick and configuration errors from turning into improve issues.
Version 1.19.8 was launched October 1 and is advisable notably for sequencer operators working with `–l2.comply with.supply`.
This just isn’t a user-facing OP token occasion. It is the form of infrastructure launch that issues exactly as a result of most customers ought to by no means discover it.
The launch 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 top is noticed.
Previously, operators utilizing the follow-source configuration may hit recurring sluggish block builds when the L1 origin modified and the required knowledge had not already been fetched via native derivation.
The new habits strikes that work earlier. If the prefetch fails, op-node logs a warning and falls again to the conventional fetch path.
That is a slender change with an apparent operational profit: fewer avoidable delays within the element chargeable for ordering Layer 2 transactions.
The wider OP Stack upkeep cycle already contains the latest required op-batcher v1.17.0 release and the rollout of Superchain interoperability on Sepolia.
Hardfork configs get stricter checks
The second main change is defensive.
op-node now refuses to start out when a customized rollup configuration prompts Jovian or a later hardfork on the identical 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 should not affected. The checks matter primarily for customized configurations that would 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 impartial chains use the software program.
Bitcoinist has additionally coated Upgrade Proposal 20 and Super Root dispute games, a part of the identical pattern towards a extra complicated multi-chain fault-proof setting.
Sepolia operators have a deadline
The launch notes additionally warn operators on Sepolia OP Stack chains that they need 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 odd customers, there is no such thing as a pockets migration or motion to take. For sequencer and node groups, the discharge is one other reminder that Layer 2 reliability is determined by maintaining a rising stack of infrastructure parts aligned with Ethereum and with one another.
—
This article was written by the News Desk and edited by Samuel Rae.
