Lido activates triggerable withdrawals on Ethereum mainnet

What happened

Lido executed the governance action that activated its triggerable-withdrawals framework on Ethereum mainnet; the subsequent v2.2.0 release identifies LIP-30 as implemented.

What changed

Lido gained an execution-layer path for initiating validator exits without relying exclusively on a node operator to cooperate, adding permissionless exit enforcement and new validator-exit control components.

What did not change

The activation was not a security incident and did not eliminate Lido's ordinary withdrawal process. The available evidence does not establish how the new mechanism will perform during stressed exit conditions.

Confirmed

• Lido Vote 192 passed and Dual Governance Proposal 5 was executed on October 2, 2025.
• Lido's official governance record states that the triggerable-withdrawals framework became live.
• The framework uses execution-layer validator-exit functionality and is intended to reduce reliance on node-operator cooperation.
• The official v2.2.0 release identifies LIP-30 as implemented and links two September 2025 security audits.

Still open

• Final deployed role assignments, GateSeal configuration, and all operative limit parameters were not independently reproduced in this review.
• The framework's usage frequency and behavior during severe validator-exit congestion remain untested by the cited records.
• Whether subsequent governance actions altered the initial configuration.

What it means for an advisor

• Supersede the design-only interpretation in the Lido memo with an executed control-change posture.
• Review validator-exit authority, permissionless enforcement, pause controls, request limits, and dependency behavior under withdrawal stress.
• Do not infer from activation or cited audits that the mechanism is safe or appropriate without separate deployed-state verification.

Previous interpretation

Prior history treated the triggerable-withdrawals framework as approved design awaiting on-chain activation.