op-node v1.19.8 fixes recurring slow block builds at L1-origin transitions and tightens hardfork activation validation; Sepolia OP Stack nodes must be at v1.19.5 or later before the October 6 Glamsterdam hardfork.
Upgrade recommended for sequencer operators using --l2.follow.source to avoid slow block builds on L1-origin changes.
op-node refuses to start on custom rollup configs that schedule hardfork activations at the same post-genesis timestamp or out of order.
Sepolia OP Stack operators must be on op-node v1.19.5 or later before the October 6 Glamsterdam hardfork.
# What changed in op-node v1.19.8
Optimism published op-node v1.19.8 on October 1. The release is focused, operational, and aimed at sequencer stability and safer upgrade handling. Optimism specifically recommends this update for sequencer operators that run with the --l2.follow.source configuration.
# Why sequencers should upgrade
Sequencers experienced recurring slow block builds when the L1 origin changed. The new op-node behavior prefetches each new L1 head's block and receipts as soon as the head is observed. That moves required data fetching earlier in the process for follow-source setups. If the prefetch fails, op-node logs a warning and falls back to the normal fetch path. The practical result is fewer avoidable delays in the component that orders L2 transactions.
# Hardfork activation validation tightened
op-node v1.19.8 adds defensive checks around hardfork activation ordering for custom rollup configurations. The node now refuses to start when:
# Sepolia deadline and related releases
# Operational impact and behavior
The hardfork ordering checks prevent startup with invalid post-genesis fork timing or misordered forks in custom rollup configs. This reduces the chance that an operator will run a node with an inconsistent upgrade sequence that could cause runtime errors or unexpected behavior.
# Practical action items for operators
# Context within the OP Stack
This release is one piece of a broader set of operator-facing updates. Recent related releases include op-batcher v1.17.0, op-reth v2.5.0 (dependency security fixes and legacy command removal), and Kona v1.8.0 (fault-proof and malformed-batch fixes). Together these updates address performance, security, and upgrade-safety across OP Stack components.
TL;DR Optimism has released op-supernode v1.0.3 as an optional operator update. The release tightens validation around hardfork activation times and rejects invalid post-genesis fork ordering in custom rollup configs. Existing chains in the Superchain registry are not affected by the configuration issue described in th
TL;DR Optimism has released op-reth v2.5.0 and recommends it for all op-reth operators. The update removes two legacy pre-Bedrock import commands and patches security issues in `rustls` and `imbl` dependencies. Operators relying on the removed import workflow need to switch to the Bedrock state-bootstrap process before
Read the latest update on Optimism Releases Required op-batcher v1.17.0 Upgrade.
TL;DR Optimism has released Kona v1.8.0 components with fixes for derivation, proof execution, TLS and preimage handling. The release prevents a malformed batch from causing Kona to derive a different chain from op-node under a specific faulty-batcher condition. Optimism recommends the release for all chains and says k
<figure data-wp-context="{"imageId":"6aba156f4c11d"}" data-wp-interactive="core/image" data-wp-key="6aba156f4c11d" class="wp-block-image size-large has-lightbox wp-lightbox-container"><img data-recalc-dims="1" fetchpriority="high" decoding="async" width="900" height="506" data-attachment-id="10397" data-permalink="http
Open the app view to save this story, compare related coverage, and continue from the same source.