Affects: Lido (protocol)
What happened
Lido tokenholders approved version 3 of the Standard Node Operator Protocol governing validator exits.
What changed
The approved standard incorporates triggerable withdrawals, expands applicability to Simple DVT, Community Staking, and future modules, and clarifies node-operator exit, configuration, responsiveness, and reporting obligations.
What did not change
The vote did not itself change the Withdrawal Queue contracts, prove universal operator implementation, or demonstrate stressed-condition exit performance.
Confirmed
- The official Lido vote concluded on October 22 with the For option prevailing.
- SNOP v3 incorporates triggerable-withdrawal responsibilities.
- The standard expands beyond the prior curated-operator context to newer staking modules.
- The approved text specifies clearer operator obligations and revised consequences for non-conformance.
Still open
- Implementation and compliance status across individual node operators and modules.
- Observed performance during large, urgent, or congested validator-exit requests.
What it means for an advisor
- Replace SNOP v2 references in Lido diligence with the approved v3 standard.
- Continue monitoring operator compliance and withdrawal timing because policy approval does not eliminate execution and queue risk.
Sources
- Proposal for Updating Lido on Ethereum Validator Exits SNOP to v3 · Lido DAO · · effective
Version 1, published . Educational research, not investment advice.