Simple DVT Module

Simple DVT Overview

📝 Summary

The Simple DVT Module (SDVTM) was introduced to battle-test Distributed Validator Technology (DVT) on Ethereum mainnet using both Obol and SSV Network implementations, while broadening participation in the Lido Node Operator set to include home and community stakers.

Since its launch, the module has demonstrated DVT operation at scale and contributed practical experience around distributed validator operations, resilience, and operator coordination. That experience has helped establish DVT as an approach now used at scale across both the Curated Module and the Community Staking Module. Across five onboarding rounds, Simple DVT grew to 72 regular clusters — 36 using Obol and 36 using SSV Network — alongside 10 Super Clusters, bringing together 330+ unique operators.

In June 2026, the Lido DAO voted the wind-down of all regular Simple DVT clusters. All 72 regular clusters have since completed validator exits. The module now consists of the 10 remaining Super Clusters, with 5 using Obol and 5 using SSV Network.

Onboarding for Simple DVT is closed. A full list of clusters and participants is available in the SDVT Registry.

🔭 Vision

The Simple DVT Module was introduced to battle-test the use of Distributed Validator Technology within the Lido protocol while broadening participation in the Node Operator set. Through its operation on Ethereum mainnet, the module provided practical experience with distributed validator operations, coordination, resilience, and the use of Obol and SSV Network at scale.

Following the wind-down of regular clusters, the Simple DVT Module continues to operate with its 10 Super Clusters.

📜 Status

🟢

Simple DVT Module on mainnet is live

🟢

Simple DVT Module on Hoodi is live

Vote Details:

Snapshot vote Staking Router Module Proposal: Simple DVT (approval)

Staking Router Module Proposal - Simple DVT

On-Chain vote Lido Vote #172 (module deployment)

Simple DVT Release

Snapshot vote Expanding the Simple DVT Module (approval)

Expanding the Simple DVT Module

Snapshot vote Wind Down Simple DVT Module Regular Clusters (approval)

Proposal: Wind Down the Simple DVT Module Regular Clusters

🏷️ Characteristics

Operators Onboarding: Closed
Bond Required: None
Rewards Rate:

Super Clusters:

10% total rewards share, broken down as:

4% allocated to treasury (2% via splitter contracts)
6% to the module (further shared between Node Operators, and the DVT infrastructure provider)

DVT: Yes, clusters currently utilize Obol and SSV Network
Stake Share Limit: 4.3%, subject to further increases by the DAO

Mainnet Registry (All Participants & Clusters):

Address List – Reward and Split Contracts

Testnets:

DVT Testnet #1	Finished	SSV: Post & Results Obol: Post & Results
DVT Testnet #2	Finished	SSV: Post & Results Obol: Post & Results
DVT Testnet #3 (Simple DVT Testnet 1)	Finished	SSV: Post & Results Obol: Post & Results
DVT Testnet #4 (Simple DVT Testnet 2)	Finished	SSV: Post & Results Obol: Post & Results

⚙️ Mechanisms

🛫 Deployments

Mainnet contracts:

💹 Economics

The Simple DVT Module’s current economic model reflects the operation of the remaining Super Clusters.

A total of 10% of staking rewards is allocated between the DAO Treasury and module participants:

4% to the DAO Treasury
6% to the module, shared between Node Operators and the relevant DVT infrastructure provider

This structure reflects the collaborative operating model of distributed validators, where multiple Node Operators jointly participate in validator operation alongside DVT infrastructure providers.

*20% is the maximum combined stake share for the 0x01 and 0x02 Community Staking Modules, approved by the Lido DAO via Snapshot in July 2026. The CSM Committee manages how this capacity is split between the two modules, adjusting each module’s on-chain limit step by step via Easy Track.

🎁 Rewards Share & Incentives

The Simple DVT Module allocates a total of 10% of staking rewards between the DAO Treasury, Node Operators, and DVT infrastructure providers.

For the currently active Super Clusters, the rewards share is distributed as follows:

4% to the DAO Treasury
6% to the Simple DVT Module, further shared between participating Node Operators and the relevant DVT infrastructure provider

This reward structure reflects the collaborative nature of operating distributed validators, where multiple Node Operators jointly operate validator infrastructure using DVT.

The specific distribution of the module share differs between Obol and SSV Network Super Clusters based on their respective infrastructure and fee mechanisms, as described in the sections below.

For technical details on how the reward share is implemented, see the Staking Router documentation on fee distribution.

Obol Economics

For Obol-based Super Clusters, the 10% total rewards share is distributed as follows:

4% to the DAO Treasury
1% to Obol
5% to participating Node Operators

Of the 4% allocated to the DAO Treasury, 2% is distributed directly through the Simple DVT Module and an additional 2% is distributed through the cluster’s reward splitter.

Obol receives its 1% reward share through the reward distribution contracts used by the Super Clusters. Rewards are processed using an Obol-developed wrapper contract together with 0xSplits-based contracts, allowing rewards to be distributed between the DAO Treasury, Obol, and participating Node Operators without requiring changes to the core Simple DVT Module contracts.

Obol-based Super Clusters do not require Node Operators to pay a separate Obol protocol service fee or maintain protocol-specific token collateral for participation.

For further technical details on the splitter contracts and reward claiming process, see the Reward Distribution section below.

SSV Network Economics

For SSV Network-based Super Clusters, the 10% total rewards share is distributed as follows:

4% to the DAO Treasury
1% to SSV Network
5% to participating Node Operators

Of the 4% allocated to the DAO Treasury, 2% is distributed directly through the Simple DVT Module and an additional 2% is distributed through the cluster’s reward splitter.

The 1% allocated to SSV Network is distributed through the reward splitter to the SSV Foundation. The SSV Foundation uses these rewards to support the network-fee runway of the SSV-based Super Clusters. This arrangement replaced the earlier grant-funded model used during the initial Simple DVT rollout.

For additional information on SSV Network fees, refer to the SSV Network documentation. More information on the reward splitter architecture is available in the Reward Distribution section below.

🏆 Reward Distribution

Node Operators in both the Obol and SSV Network Super clusters claim their rewards via the usage of 0xsplits-based contracts which receive staking rewards from the Lido protocol on a daily basis. During the initial setup, participants are asked to provide two addresses: an Individual Manager Address and an Individual Reward Address.

Workflow

Generation of Multi-Signature:

Each Super cluster chooses a “Cluster Coordinator”, a participant that is responsible for creating a Safe multi-sig and initializing the Distributed Key Generation (DKG) ceremony for the cluster. Each cluster’s SAFE also consists of a 5/7 threshold, and represents the cluster in the Lido Node Operator registry.
Next, cluster participants submit and verify an “Individual Manager Address” with Lido, used for signing messages in their Safe and DVT interface, and an optional “Individual Reward Address” that participants can use to receive staking rewards to in lieu of their Individual Manager Address.
Once the cluster participants’ setup of addresses is completed, Cluster Coordinators create their respective cluster's SAFE and participants generate validator keys via DKG, configure their nodes, and submit the keys to the Simple DVT Module.

Generation of Splitter Contracts & Reward Distribution Mechanics:

During the cluster setup phase, each participant submits their "Individual Manager Address" and an optional "Individual Reward Address", leading to the generation of cluster-specific multi-sigs representing their Cluster Node Operator entries, and the deployment of reward splitter contracts. The "Individual Reward Address" is then utilized to claim rewards from the splitter contract.
To simplify the reward claiming process for Simple DVT Node Operators, both the Obol and SSV Network clusters will utilize two sets of smart contracts:

A wrapper developed by Obol that wraps stETH rewards into wstETH, charges an (optional) fee, and forwards the remainder of the wstETH to the next smart contract,
An 0xsplits set of smart contracts that allows for the distribution of rewards between participants.

The Obol wrapper contract was audited by a solo auditor (obol-splits/audit at main · ObolNetwork/obol-splits · GitHub). A wrapper contract is created via the ObolLidoSplit factory and this contract is specified as each cluster’s reward address. This contract is responsible for wrapping stETH rewards to wstETH and when applicable, gives the DVT provider their reward share. This contract can be called by anyone, and will transfer wstETH to a split contract created via another factory (the main 0xsplit contract), from where each individual cluster participant can claim.

🧰 Validator Management

The operationalization of validators within Simple DVT involves a collaborative approach by Node Operators through their participation in respective clusters. The DAO approved use of the cover fund as a partial backstop in the event of significant Simple DVT Node Operator penalties through a Snapshot vote.

Roles and Responsibilities

Node Operators: Individuals or entities operating nodes are tasked with the continuous running and maintenance of their nodes. Node Operators are responsible for keeping their client versions up-to-date, and for maintaining proper configurations.
Clusters: Clusters, comprising of multiple Node Operators, adopt a self-management ethos. Each cluster is responsible for coordinating among its participants to select a Cluster Coordinator, sign, and verify all relevant transactions pertaining to their cluster.

Configuration and Guidelines

While there is a default Lido configuration for SDVT Obol Mainnet provided to assist in the initial setup, these configurations are not exhaustive. Clusters and Node Operators are encouraged to:

Review and Update Configurations: Regularly review the provided configurations against their specific operational needs. This may involve customizing settings to optimize performance, security, and reliability.
Manage MEV Relays and Oracle Addresses: Specifically, configurations related to MEV relays, oracle addresses, and other network-specific parameters should be periodically assessed and updated to reflect the current operational environment.
Software Version Management: For those using existing nodes, it is crucial to ensure that all software components are up-to-date. This includes the node software itself, any related dependencies, and the configurations derived from the Obol mainnet guide.

🛠️ Committees

The DAO is aided in the maintenance of the Simple DVT Module by two DAO sub-groups: the Curated Module Committee (CMC) and the Simple DVT Module Committee (SDVTMC), although the sub-groups do not directly control the module.

Management of the Simple DVT Module is at the control of the DAO, and all Module operations occur through the use of Easy Track Motions which are a form of optimistic governance which allows for any LDO token-holder to object to (veto) actions proposed by the SDVTMC or clusters which a token holder may not be in agreement with.

🗣️ Curated Module Committee (CMC)

Duties

The CMC is tasked with the curation and of proposal of clusters for the Simple DVT Module deployment on mainnet. This includes the evaluation of performance metrics from DVT testnets and making recommendations based on these insights, in coordination with the Simple DVT testnet coordinators who have detailed insights into participant behavior during the testnet.

Activities:

Reviewing the results of the testnet trials in collaboration with DVT providers like Obol and SSV Network to assess the readiness and efficiency of clusters for mainnet deployment.
Engaging in discussions and decision-making processes to recommend increases in validators operated by clusters based on their performance and contribution to the network's resilience.
Providing transparent updates and proposals to the Lido DAO and community via research forum and governance channels.

Where an operator replacement is required, the CMC may assess Node Operators from the pool of previous Simple DVT participants. Considerations may include operational performance, responsiveness and engagement, infrastructure characteristics and geographic distribution, and participation in other clusters.

Relevant proposals, recommendations, and operational updates are communicated and discussed publicly through the Lido Research Forum and applicable governance channels.

👥 Simple DVT Module Committee (SDVTMC)

The Simple DVT Module Committee (SDVTMC) is a multi-signature committee responsible for executing permitted Simple DVT Module operations through Easy Track.

Following the transition of Simple DVT oversight to the CMC, the SDVTMC’s role is primarily focused on the on-chain execution of applicable operational changes coordinated through the CMC.

Permitted Easy Track actions include changes to Simple DVT Node Operator Registry entries and cluster properties, such as activating or deactivating Node Operator entries, adjusting validator key limits, and updating manager or reward addresses. All Easy Track motions remain subject to optimistic DAO governance and can be vetoed by LDO token holders.

The SDVTMC multi-sig address is: 0x08637515E85A4633E23dfc7861e2A9f53af640f7

Committee actions can be monitored on-chain and through the applicable Lido governance channels.

Resources:

Research Forum Post

🤝 Node Operators

The Simple DVT Module currently consists of 10 Super Clusters - 5 using Obol and 5 using SSV Network. Each Super Cluster is composed of multiple Node Operators that collaboratively operate distributed validators.

Super Cluster participants include a diverse set of community stakers and professional Node Operators with experience operating distributed validator infrastructure.

For information on the current Super Clusters and their participating Node Operators, as well as the historical Simple DVT clusters and participants, refer to the SDVT Registry.

🤝 Onboarding

Onboarding for the Simple DVT Module is closed.

The Simple DVT onboarding program began in Q4 2023 with Obol and SSV Network testnets, and concluded after multiple testnet rounds. Across the program, 72 regular clusters and 10 Super Clusters were onboarded to the module.

Following the DAO-approved wind-down of the regular clusters in 2026, no new clusters or Node Operators are being onboarded through the Simple DVT onboarding program.

🔮 Oracles

Oracle daemon for Lido monitors the state of the protocol across both layers and submitting regular update reports to the Lido smart contracts.

There are two modules in the oracle:

Accounting module updates the protocol TVL, distributes node-operator rewards, updates information about the number of exited and stuck validators and processes user withdrawal requests. The accounting oracle also makes decision to turn on/off the bunker.
Ejector module requests Lido validators to eject via events in Execution Layer when the protocol requires additional funds to process user withdrawals.

https://docs.lido.fi/deployed-contracts/#oracle-contracts

https://github.com/lidofinance/lido-oracle?tab=readme-ov-file#how-it-works