1 min read

Optimism Recommends op-node v1.19.8 Ahead of Glamsterdam Upgrade

The release moves some Ethereum block data fetching earlier to reduce delays. Sepolia OP Stack operators need op-node v1.19.5 or later before the Oct. 6 hardfork.

Mentioned assets
A compact network gateway with a fiber connection and status light / TokenPost.ai
A compact network gateway with a fiber connection and status light / TokenPost.ai

Optimism released op-node v1.19.8 on Oct. 1, recommending the update for sequencer operators to help reduce delays when Ethereum’s latest block becomes the origin for an OP Stack chain.

The recommendation is especially relevant to operators using the --l2.follow.source setting. The update fetches a newly observed Ethereum layer 1 block and its receipts before the chain needs them as its origin. If that early fetch fails, the node issues a warning and uses its normal fetch process.

The release also rejects certain invalid hardfork schedules in custom rollup configurations. A custom configuration fails validation if Jovian or any subsequent hardfork activates at its predecessor’s post-genesis timestamp, or if any fork is scheduled before the one preceding it. No chain in the embedded Superchain registry is affected, while custom configurations that break these rules need correction before an upgrade.

Sepolia OP Stack operators need at least op-node v1.19.5 ahead of the Oct. 6 Glamsterdam hardfork. The minimum version requirement does not make v1.19.8 mandatory for every operator.

Simon Yoon

Reporter

Simon Yoon reports on blockchain technology for TokenPost. Send corrections or tips to info@tokenpost.com.

Loading…