Optimism Recommends op-node v1.19.8 For Sequencers Before Glamsterdam
Bitcoinist reports Optimism released four OP Stack updates on October 1, including op-node v1.19.8 for sequencers ahead of the October 6 Glamsterdam hardfork.
Why it matters
The releases are routine OP Stack maintenance, and Bitcoinist states op-node v1.19.8 has no user-facing OP token effect. The one deadline with a date attached is the October 6 Glamsterdam hardfork, where Sepolia operators must already be on op-node v1.19.5 or later, and the op-reth command removal breaks workflows for anyone still importing pre-Bedrock history.
Key facts
Optimism released op-node v1.19.8 on October 1 and recommends it particularly for sequencer operators using –l2.follow.source.
Reported by Bitcoinist
Optimism says sequencers on v1.19.8 prefetch each new L1 head's block and receipts as soon as the head is observed, logging a warning and falling back to the normal fetch path if the prefetch fails.
Reported by Bitcoinist
Sepolia OP Stack operators must run op-node v1.19.5 or later before the October 6 Glamsterdam hardfork.
Reported by Bitcoinist
Optimism published op-reth v2.5.0 on October 1 and recommends it for all op-reth operators.
Reported by Bitcoinist
op-reth v2.5.0 removes the pre-Bedrock commands import-op and import-receipts-op, and operators on that workflow must move to the Bedrock state-bootstrap process before upgrading.
Reported by Bitcoinist
op-reth v2.5.0 patches security issues in the rustls and imbl dependencies.
Reported by Bitcoinist
Optimism published Kona host v1.8.0 alongside the matching client on October 1 and recommends it for all chains, with kona-host run against matching kona-client v1.8.0 absolute prestates.
Reported by Bitcoinist
Optimism says op-supernode v1.0.3, published October 1 as an optional release, refuses virtual-node configurations that activate two hardforks at the same post-genesis timestamp from Jovian onward, while chains already in the Superchain registry are unaffected.
Reported by Bitcoinist
What happened
Bitcoinist reported on October 2 that Optimism released four OP Stack components on October 1. The headline item is op-node v1.19.8, which Optimism recommends particularly for sequencer operators running with the –l2.follow.source configuration; Optimism says sequencers will now prefetch each new L1 head's block and receipts as soon as the head is observed, falling back to the normal fetch path with a logged warning if the prefetch fails. Bitcoinist also reports that Sepolia OP Stack operators must run op-node v1.19.5 or later before the October 6 Glamsterdam hardfork. Three further releases came out the same day: op-reth v2.5.0, recommended for all op-reth operators, which removes the pre-Bedrock import commands import-op and import-receipts-op and patches security issues in the rustls and imbl dependencies, with operators on that workflow told to move to the Bedrock state-bootstrap process first; Kona host v1.8.0 with its matching client, recommended for all chains, which after Holocene checks the parent hash of each singular batch against the safe head the way op-node does; and op-supernode v1.0.3, an optional release that rejects virtual-node configurations activating two post-genesis forks at the same timestamp. Optimism says fault proofs are unaffected unless the batcher misbehaves, and says chains already in the Superchain registry are unaffected by the supernode configuration issue. Bitcoinist describes op-node v1.19.8 as an infrastructure release with no user-facing OP token effect. Only Bitcoinist covers these releases, so the details rest on a single outlet.
How the story developed
- Official statement
Optimism ships four OP Stack updates on October 1
op-node v1.19.8, op-reth v2.5.0, Kona v1.8.0 and op-supernode v1.0.3 are all published on the same day.
- First report
First report by Bitcoinist
Optimism Recommends op-node v1.19.8 For Sequencers Ahead Of Glamsterdam
- Update
Bitcoinist reports the release cycle
Four stories covering the same day of OP Stack maintenance, leading with the op-node sequencer recommendation.
- Update
Glamsterdam hardfork deadline for Sepolia operators
Sepolia OP Stack operators must be on op-node v1.19.5 or later before the hardfork.
How coverage built up
Independent sources over time, counted the way the consensus panel counts them: a republication of a wire story does not move the line.
- 2 Oct 2026, 08:41 UTC: Bitcoinist — 1 independent source, 1 reports
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| Bitcoinist Crypto media | Optimism Recommends op-node v1.19.8 For Sequencers Ahead Of Glamsterdam | Original | |
| Bitcoinist Crypto media | Optimism Ships op-reth v2.5.0 With Dependency Security Fixes And Legacy Command Removal | Independent | |
| Bitcoinist Crypto media | Optimism Kona v1.8.0 Tightens Fault-Proof Execution And Malformed Batch Handling | Independent | |
| Bitcoinist Crypto media | Optimism op-supernode v1.0.3 Adds Stricter Hardfork Configuration Checks | Independent |