Optimism just shipped four client patches. kona-client is now required before Glamsterdam, and interop_ is officially live infrastructure.
The release notes look routine. But kona-client v1.5.2 has a hard gate, and the interop_ namespace just became something every L2 operator needs to track.
CryptoVibe Desk · optimism · superchain · op-stack
- →Optimism published op-reth v2.2.5, kona-client v1.5.2, op-proposer v1.16.3, and op-node v1.18.2 this week, each carrying interop-related changes across the OP Stack.
- →kona-client v1.5.2 is a hard requirement before Glamsterdam activates on L1, making it the first Superchain upgrade in this cluster that operators cannot treat as optional.
- →Watch the interop_ RPC namespace in op-reth: it is the first public API surface for Superchain cross-chain messaging, and a stable interface spec does not yet exist.
- FCU (forkchoiceUpdated) → The call an Ethereum consensus client makes to tell the execution client which block is the current chain head; a bug here means a client can follow the wrong chain.
- Glamsterdam → The next planned Ethereum mainnet upgrade after Pectra; OP Stack clients must be compatible with its rule changes before it activates on L1.
- kona-client → Optimism's Rust-based program that verifies whether a state transition on an OP Stack chain was valid, used when someone disputes a claim about what the chain did.
- interop_ RPC namespace → A new set of API endpoints in op-reth that exposes cross-chain message data, the first interface for apps that want to query the Superchain's shared messaging layer.
Optimism shipped four client releases in the past week. Most look like maintenance.
Read the release notes as a set and the pattern is clear. This is a coordinated release train, wiring up Superchain interop one component at a time. The dependency graph is becoming real infrastructure.
Start with op-reth v2.2.5, published today. It bumps the reth dependency to pick up a fix for an FCU backfill-target bug, per reth PR #24159 from Paradigm. More important: it quietly adds the `interop_` RPC namespace.
That namespace didn't exist before. It's the first API surface where apps can query cross-chain message data on the Superchain. What actually ships here is the scaffolding. The full interop spec comes later.
The more consequential release is kona-client v1.5.2, published yesterday. The release notes say it is required before Glamsterdam activates on L1. That's a different class of upgrade.
Most OP Stack releases give operators flexibility on timing. This one has a hard gate. If you run an OP Stack chain and skip this update, your fault proof client will be incompatible with L1 once Glamsterdam lands.
op-proposer v1.16.3 and op-node v1.18.2 are softer. Both are optional, both carry interop preparation work and dependency bumps. The op-proposer notes say non-interop deployments mainly get an op-geth bump. Small blast radius if you're not on the interop path.
The tradeoff across this cluster is timeline pressure versus operator flexibility. Glamsterdam isn't live yet, but the required update exists now. That's the right engineering call: build in lead time before the deadline, not after. The risk is that operators who process releases without reading notes won't distinguish required from optional. That distinction matters here.
If you operate an OP Stack chain, read the kona-client v1.5.2 notes before your next maintenance window. The FCU fix in op-reth is worth flagging separately. A client that follows the wrong forkchoice target is a correctness problem, not a performance one.
The `interop_` namespace is worth bookmarking. It's the earliest visible signal of what the Superchain messaging API looks like at the RPC layer. The engineers know what's coming. The marketing announcement arrives later.
Optimism scattered the required-versus-optional upgrade signal across four separate release pages instead of a single versioned compatibility matrix. That's the kind of process gap that turns a routine operator task into an L1 compatibility incident.
Watch for an official API specification for the `interop_` RPC namespace before Glamsterdam activates on L1. If Optimism ships without documenting a stable interface, every tool built against the current namespace is provisional by design.
Primary links and supporting reads used by the desk for this story.
Forward this.
