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 upgrading.

Optimism’s latest op-reth release is a maintenance update with two things infrastructure teams tend to take seriously: breaking command removal and dependency security patches.

Version 2.5.0 was published October 1 and is recommended for all op-reth operators.

The release does not change the economic rules of the OP Stack. It changes the software used to execute and maintain those rules.

Pre-Bedrock import commands are gone

The most visible breaking change is the removal of `import-op` and `import-receipts-op`.

Those commands were used for importing legacy pre-Bedrock OVM history. Operators who still depend on that workflow need to move to the Bedrock state-bootstrap process before upgrading, with pre-Bedrock history served from an l2geth instance.

This is the kind of cleanup mature chains eventually have to perform. Old compatibility paths are useful during migrations, but maintaining them indefinitely increases software complexity.

Bitcoinist recently covered another piece of the same maintenance cycle when Optimism shipped a required op-batcher upgrade and when native account abstraction work moved toward the OP Stack.

Two dependency vulnerabilities are patched

op-reth v2.5.0 updates `rustls` to version 0.23.45 to address RUSTSEC-2026-0285. The issue involved TLS 1.3 handshake messages being accepted at the wrong encryption level rather than the connection being closed.

The release notes state that the handshake remained authenticated, meaning the bug did not let an attacker alter or complete the handshake, but operators still get the patched dependency.

The update also moves `imbl` to 7.0.2 for RUSTSEC-2026-0292, fixing a double-free condition in a component used by the transaction pool when an element destructor panics.

Those are software-security fixes, not evidence that an OP Stack chain was actively exploited.

Infrastructure upgrades are becoming a steady operational workload

Layer 2 networks increasingly look less like a single protocol and more like a suite of coordinated programs.

Sequencers, batchers, execution clients, fault-proof components and cross-chain services all need their own release cycles. Bitcoinist’s coverage of Superchain interoperability testing shows why that stack keeps expanding.

For end users, op-reth v2.5.0 should be invisible. For node teams, the release notes are clear: update the client, account for the removed legacy commands and take the security patches.

—

This article was written by the News Desk and edited by Samuel Rae.

TL;DR

• Lido DAO Vote #214 has passed with 58.2 million LDO participating in favor.
• The vote implements Dual Governance V1 parameters, giving stETH holders a new mechanism to contest certain governance actions.
• The associated emergency governance delay has been extended to 14 days.

Lido’s long-running effort to give stETH holders more influence over protocol governance has moved another step forward.

Onchain Vote #214 has passed, implementing parameters associated with Lido’s Dual Governance system on Ethereum mainnet.

The vote received support from 58.2 million LDO participating tokens.

Dual Governance Creates A Second Check On LDO Holders

Traditional DAO governance gives voting power to holders of the governance token.

For Lido, that means LDO.

The complication is that the people economically exposed to the staking protocol are not necessarily the same people holding large amounts of LDO.

stETH holders may have substantial value inside Lido while having little direct ability to stop governance decisions that affect the protocol.

Dual Governance is designed to narrow that gap.

The framework gives stETH holders a mechanism to contest or delay certain governance actions before they are executed.

That does not replace LDO voting.

It creates an additional check around it.

The idea is particularly important for a liquid staking protocol because governance controls smart contracts handling very large amounts of user-deposited ETH.

The Delay Window Is Part Of The Security Model

Vote #214 also extends the relevant emergency governance delay window to 14 days.

A longer delay gives stakeholders more time to respond when an action is disputed.

That can make governance slower.

It can also make a hostile or controversial change harder to rush through before affected users have time to react.

Lido has been developing Dual Governance as a way to reduce one of the structural risks around decentralized protocols: governance-token holders making decisions that may not align with the interests of users whose assets sit inside the system.

The latest vote does not make Lido governance perfectly decentralized or remove every governance risk.

It does change the balance.

LDO remains the governance token, but stETH holders now have a more meaningful role in the safety architecture around major decisions.

For a protocol whose main product represents staked ETH, that is a significant shift in who gets a voice when governance and user capital collide.

This article was written by the News Desk and edited by Samuel Rae.