Proposal for Updating Lido on Ethereum Validator Exits SNOP to v3

Summary

This proposal seeks the community’s support to update the currently in effect Standard Node Operator Protocol (SNOP) on Validator Exits v2 (Snapshot) to the proposed SNOP on Validator Exits v3.

Context & Motivation

The current version of the SNOP on Validator Exits dates back to when Ethereum’s withdrawal and exit mechanics were still largely static. Since then, several important developments have emerged:

• The Staking Router architecture continues to evolve, enabling new modules such as SDVT and CSM.
• The Pectra upgrade introduced Triggerable Withdrawals, expanding the flexibility of how withdrawals can be executed by protocols such as Lido.
• Ongoing discussions around validator sets require clearer guidance for Node Operators (NOs).

This proposal ensures that the SNOP on Validator Exits remains up to date with these protocol advancements and provides NOs with consistent operational expectations aligned with the future of Ethereum and the Lido protocol.

The proposed v3 builds on prior governance-approved standards, integrates community and contributor feedback, and adopts the standardized structure established across other SNOPs for clarity and long-term maintainability.

Overview of Changes & Additions

The main changes and additions include:

• Integration of Triggerable Withdrawals: adapting NO responsibilities and processes to reflect the new mechanism for externally triggered withdrawals.
• Clarification of Exit Procedures: addressing how the latest changes in the protocol affect exit behavior and reporting.
• Standardized Structure and Definitions: bringing the SNOP into the unified documentation framework used across all recent revisions.
• Extended Scope: ensuring applicability to NOs participating through Simple DVT, Community Staking, and future module types.
• Explicit NO Responsibilities: clearer obligations around exit initiation, responsiveness to withdrawal triggers, and timely execution.
• Updated Per-Module Consequences: revised accountability framework for non-conformance, reflecting new operational tooling and staking module designs.

NO Responsibilities

The key responsibilities arising for NOs using the Lido protocol with respect to validator exits are as follows:

• Respond promptly to and, where applicable, initiate triggerable withdrawal events in accordance with the protocol’s operational timelines.
• Maintain accurate exit and withdrawal configuration for all validators under their operation.
• Ensure transparent communication and reporting when exit processes or triggers encounter issues.
• Comply with operational best practices for withdrawal handling, safeguarding user funds, and validator integrity.

Official References

The full text of the proposed Standard Node Operator Protocol (SNOP) on Validator Exits v3 is available through the following sources:

• IPFS link - primary reference, to serve as the single source of truth if the proposal is approved
• GitHub pull request link

Vote Outcomes

• If the “For” option wins:

  The proposed Standard Node Operator Protocol (SNOP) on Validator Exits v3 will be used as the primary reference for NO interactions with the Lido protocol regarding validator exits and withdrawals, effective immediately following the conclusion of the vote.

• If the “Against” option wins:

  The SNOP on Validator Exits v2 will remain in effect, and a revised version of v3 will be prepared based on community feedback for potential resubmission in a future vote.