Proposal for Updating Lido on Ethereum SNOPs: Block Proposals v3 to v4, and Validator Exits v3 to v4

Proposals
1

Dear Lido community,

This post proposes updates to two Lido on Ethereum Standard Node Operator Protocols (SNOPs): the SNOP on Block Proposals (v3 → v4) and the SNOP on Validator Exits (v3 → v4).

Both policies are being revised jointly, as the primary driver for this update is the same: the introduction of Curated Module v2 (CMv2). With CMv2 bringing a new operator classification structure, a bonding mechanism, and native 0x02 validator support, both SNOPs required extension to cover operators and validators participating under the new module.

Why now?

The v3 versions of both SNOPs were written ahead of CMv2’s design being finalized. At the time, scope was extended to cover Simple DVT, Community Staking, and potential future modules; but CMv2 introduces enough structural change that it warrants explicit coverage in both documents.

Specifically, CMv2’s support for 0x02 validators (with effective balances up to 2,048 ETH), the consolidation of CMv1 validators into CMv2, and the introduction of CMC as the primary mechanism for accountability in the Curated Module all have direct implications for how block proposals are handled and how validator exits are triggered and reported.

Main changes - Block Proposals v3 → v4

  • Extension of scope to Node Operators participating through CMv2
  • Updated validator definitions to account for 0x02 validators and high-balance consolidations
  • Clarification of operator responsibilities around block proposals during the CMv1→CMv2 migration period

Main changes - Validator Exits v3 → v4

  • Extension of scope to Node Operators participating through CMv2
  • Updated exit procedures to reflect 0x02 validator mechanics and the higher effective balances introduced by Pectra
  • Clarification of how consolidations interact with exit prioritization and triggerable withdrawal flows
  • Updated consequence framework to reflect CMv2’s penalty and bonding structure

Next steps

The drafts are not final, and we invite community feedback to ensure both policies accurately reflect the new module’s operational and technical realities. If no objections are raised, the next step will be a Snapshot vote during the June cycle to ratify the new SNOPs. It is important to note, the successful application of the new SNOPs depends on the related CMv2 and SRv3 votes.
You can review the full drafts here:

1 Like