The shipped OP Stack releases are op-supernode v1.0.2, op-reth v2.4.4, op-node v1.19.7, op-batcher v1.17.0, and kona-node v1.7.0. The publisher labels op-batcher as required for its operators and op-supernode as recommended. Scope-wise, the batcher adds a gas limit that is valid under both pre-Glamsterdam and Glamsterdam floor-data-gas rules; Kona includes reliability and dependency-security changes (stronger overlap validation, a blob-backed-channel SIGSEGV restart-loop fix, replacements for vulnerable Yamux and Hickory, and bounded gossip metrics); and Supernode removes cross_unsafe_l2 from one sync-status response while retaining separate message-safety semantics. These points come from the official ethereum-optimism/optimism release records and do not constitute a protocol activation.
Operative status at our evidence cutoff of 12 September 2026 18:14:30 IST: this is released software recorded by the official ethereum-optimism/optimism repository, with the relevant entries timestamped between 12 September 2026 00:04:48 and 00:05:45 IST. The records do not establish exploitation, incident, loss, affected deployments, adoption, or India-specific operator inventory. A World Chain Karst warning noted in the materials is chain-specific. This release bundle is not an “Upgrade 20” activation.
Release bundle and exact status
According to the official ethereum-optimism/optimism release records, five components were released in close succession: op-supernode v1.0.2, op-reth v2.4.4, op-node v1.19.7, op-batcher v1.17.0, and kona-node v1.7.0. The publisher explicitly labels the op-batcher release as required for its operators and op-supernode as recommended. The remaining versions are presented as releases without an operator mandate label in the notes we reviewed.
State classification is important: these items are in a released state, not merely proposed or merged, yet they are also not a governance or chainwide protocol activation. The records do not evidence adoption rates or impacts, and they do not show incidents or losses. The World Chain Karst warning is explicitly chain-specific. Our reading window ends at 12 September 2026 18:14:30 IST.
Version-by-version operator map
Component versions shipped are: op-batcher v1.17.0, op-node v1.19.7, op-reth v2.4.4, kona-node v1.7.0, and op-supernode v1.0.2. Per the publisher’s labels in the official release records, op-batcher is required for its operators, while op-supernode is recommended. No additional operator mandates are stated for op-node, op-reth, or kona-node in the materials we reviewed.
In functional scope terms, the op-batcher addition of a gas limit that is valid across both pre-Glamsterdam and Glamsterdam floor-data-gas rule sets is a compatibility measure. kona-node notes emphasize reliability and dependency-security updates (overlap validation strengthening; fix for a blob-backed-channel SIGSEGV restart-loop; replacing vulnerable Yamux and Hickory; and bounding gossip metrics), while op-supernode removes cross_unsafe_l2 from one sync-status response but keeps distinct message-safety semantics intact.
“Operators” here refers to the maintainers running the respective services (e.g., batcher operators), not to all L2 participants. The labels communicate the publisher’s operational guidance for those roles; they are not on-chain enforcement and do not signify a protocol activation or an effective state change at the network level.
Why the batcher is labelled required
The release notes designate op-batcher v1.17.0 as required for its operators because it introduces a gas limit that remains valid under both the pre-Glamsterdam and Glamsterdam floor-data-gas rules. That dual-rule compatibility narrows the risk of misalignment when submitting data across environments that may reference either set of rules during their transition timelines.
This label is about operator correctness and cross-rule compatibility, not about activating new consensus logic. The publisher’s “required for its operators” phrasing is an operational directive to batcher operators to maintain correctness across the specified rule regimes.
Practically, the reason to prioritize this update is to maintain consistent batch submission behavior as fee-floor treatments evolve. For additional context on interpreting labels like “required” or “recommended,” see our methodology explainer at /article/method-reading-crypto-protocol-upgrade-notices. We do not assert any incident, exploitation, or loss related to pre-update batcher behavior, as none is established in the official records.
Kona reliability and dependency-security changes
The kona-node v1.7.0 notes, per the official release records, emphasize reliability hardening and dependency-security updates: stronger overlap validation, a fix for a blob-backed-channel SIGSEGV restart-loop, replacement of vulnerable Yamux and Hickory components, and bounded gossip metrics. These are stated as shipped changes; they are not tied to a reported incident in the records we reviewed.
Dependency-security updates reduce exposure to known-vulnerable libraries or subsystems. The records specifically characterize Yamux and Hickory as vulnerable and indicate they were replaced, which is a targeted supply-chain mitigation action. Bounded gossip metrics aim to keep instrumentation within safe limits, supporting observability without destabilizing the node.
These changes are in a released state with unknown adoption. They matter for any operator running Kona, including prospective operators in large markets such as India, but the records do not establish any India-specific exposure or inventory. For a broader view of code-execution and dependency risk pathways, see /article/smart-contracts-code-execution-operational-risk.
Supernode response-field change
op-supernode v1.0.2 removes the cross_unsafe_l2 field from one sync-status response. The official records also state that separate message-safety semantics are retained, which limits the surface of change to that specific response field rather than altering safety definitions elsewhere.
For operators whose monitoring or integration tools referenced that field, this is a compatibility note, not a chain-level change. The label for this release is “recommended,” and the records do not present evidence of breakage, incident, or loss; nonetheless, attention to response-shape expectations is prudent when upgrading supporting services.
Unknown adoption, scope and India deployment limits
At the 12 September 2026 18:14:30 IST evidence cutoff, the official records do not show adoption metrics, affected deployments, exploitation, or loss. Thus, adoption remains unknown. The World Chain Karst warning noted in the materials is identified as chain-specific, not a general OP Stack incident.
As for India, no India-specific operator inventory or deployment exposure is established in the records. India hosts active developers and infrastructure operators across L1 and L2 ecosystems, but we do not infer OP Stack update uptake from that general market activity.
We classify the bundle as released software with unknown adoption and non-activation status. If future official statements from the publisher or major operators document deployment decisions, that would shift the adoption status from unknown to reported or verified. For how we track and label uncertainty, see /article/how-cryptossinsights-labels-uncertainty.
Reading release labels without confusing activation or exploitation
Publisher labels such as “required for its operators” and “recommended” convey operational guidance within the software ecosystem but are distinct from on-chain protocol governance or activation events. The releases discussed here are not Upgrade 20 activations and are not presented with effective block heights or rollup-wide toggles in the records we reviewed.
Evidence that would change the status includes: official statements from the publisher or core operators confirming broad deployment; repository or change management notes indicating enforced flags, rollup configuration activation, or chain parameters becoming effective; and credible incident reporting from named organizations establishing exploitation, outages, or loss attributable to pre-update behavior. Absent such records, the correct read is “released; adoption unknown; no established incident.”
When assessing L2 software releases versus protocol activations, separating “code available” from “rules effective” helps avoid overstatements. For foundational background on how L1 and L2 governance and deployment flows differ, see /article/layer-1-layer-2-networks-comparison. The evidence supports interpreting the present bundle strictly as released code with stated operator labels and clearly scoped compatibility and dependency-security notes from the official ethereum-optimism/optimism records.