Staking Router Module Proposal: Simple DVT

Proposals
102

Hello everyone again,

DKG v3.0.2

I am following up on previous announcement to let the Lido community know that the SSV Labs team has released a new version of the DKG software:

This is a patch version, whose main significant change is an update on a library dependency. This was necessary, as during tests on Simple DVT permanent testnet, it became evident that in some specific CPU configurations (most notably: old CPUs, or very low spec cloud VPSs) the cluster could not successfully complete DKG ceremonies.

Investigation led to isolate the issue and found the source to be bug of a specific version of a dependency library.

Thank you.

5 Likes
103

An Easy Track motion has just gone live via the Simple DVT Module Committee that would add the 15 Lido x SSV Cohort 3 clusters to the Simple DVT Node Operator Registry on mainnet.

In addition to signed messages confirming each participant’s agreement to the Operating Rules of the Simple DVT Module for Lido x SSV Node Operators, the following link contains sheets showing Cluster Manager Addresses, Wrappers, and 0xSplits addresses well as all of the participant Individual Manager and Individual Reward Addresses tied to each cluster: Public Master Address Form (SSV Mainnet) - Google Sheets

If this motion passes, it is expected a subsequent set of motions will be created over the next weeks to raise the key limits of these SSV Simple DVT clusters to 5 validators. Once validators are deposited to, a monitoring period will be in place to assess cluster performance, and an update will be made in this thread to share the results of the first 30 days.

4 Likes
104

Two new Easy Tracks are live:

  1. To increase the key limit for the Vivacious Viper cluster to 85 (80 keys active).
  2. To disable the target limit for the Tranquil Turtle cluster.

A follow up motion will be created shortly to increase the key limit for the Tranquil Turtle cluster to 5 keys. After verifying the keys activate smoothly, the cluster limit will again be raised to the previous level before the exit as mentioned in the incident report above.

2 Likes
105

Summary

This update serves as the third performance report for the Lido x SSV Quiet Quetzal cluster, with a report to come in the next weeks for the 8 other Lido x SSV Cohort 2 clusters active on mainnet via the Simple DVT Module. Given continued improvement in the clusters performance, it is proposed that the key limits for Quiet quetzal are raised to 80 validators along with the other C2 clusters.

Performance Analysis

The performance monitoring period for all of Lido x SSV Cohort 2 began on Oct 18th, the day the 9 clusters had active validators.

Since that time, as per Rated, Quiet Quetzal’s average uptime stands at 99.71%, aggregate Block Proposal Success Rate of 100%, and Average Validator Effectiveness is 91.79%. The aggregate Validator Effectiveness has increased from 89.5% as shared in the February 4 performance report. The performance of the cluster has come back in line with the other clusters, with a 97.64% 30D RAVER score.

For a detailed overview of cluster level metrics, see the analysis: SSV Cohort 2 Performance Metrics - Google Sheets

Proposed Next Steps

It is proposed that the key limits for Quiet Quetzalbe raised to a maximum of 80 validators, in-line with the rest of Cohort 2.

The relevant Easy Track motion for the key limit raises would be communicated in this thread and would follow the default approach of being veteoable by LDO holders over a 72 hour period.

This begins a 7 day discussion period for the DAO to consider the performance report and proposal to raise key limits to 80 validators for Quiet Quetzal.

106

This update serves as the second performance report for the Lido x Obol Whistling Wolf Cluster. A follow up report will be made on the other 13 Lido x Obol C2 clusters. Given improvement in the cluster’s Block Proposal Success Rate, it is proposed that the key limits for Whistling Wolf are raised to 80 validators along with the other C2 clusters.

Performance Analysis

The performance monitoring period for Whistling Wolf, along with the other 13 Clusters began on August 15th.

During this time, as per Rated, average uptime stands at 99.92%, aggregate Block Proposal Success Rate of 86.54%, and Average Validator Effectiveness is 95.85%. The Block Proposal Success Rate has increased from 57.14% as noted in the prior performance report.

For a detailed overview of cluster level metrics & the list of validator keys, see the analysis: Obol Cohort 2 Performance Metrics - Google Sheets

Proposed Next Steps

Given the improved Block Proposal Success Rate, it is proposed that Whistling Wolf’s key limit be increased to 80 validators along with the other C2 clusters.

The relevant Easy Track motions for these key limit raises would be communicated in this thread and would follow the default approach of being veteoable by LDO holders over a 72 hour period.

This begins a 7 day discussion period for the DAO to consider the performance report and proposal to raise the key limits for Whistling Wolf to 80 validators.

1 Like
107

Two Easy Track motions are now live:

  1. The first to set the key limits for Obol Tranquil Turtle and Whistling Wolf to 80 validators.
  2. The second to set the key limits for the first 12/15 SSV C3 clusters to 5 validators. The other 3 clusters are expected to be ready in the coming days.
3 Likes
108

Ethereal Elf Incident Report - 16/4/25

On 16/4/25, a NO error in initiating the voluntary exits for the Lido x Obol Majestic Moose clusters took place, improperly leading to the Lido x Obol Ethereal Elf cluster’s validators to be exited.

No stakers funds are at risk because of this incident and there is no material impact to the protocol. The ETH from these validators will cycle through the Lido buffer as it normally does when a validator is exited.

As of now, all active validators in both the Majestic Moose and Ethereal Elf clusters have been exited (a total of 454 validators vs. 6700 in SDVT & 289k total).

The Majestic Moose cluster was attempting to exit their validators as a result of one of the cluster’s participants, Yellowbee, having gone inactive. However, when running the exit command, the Cluster Coordinator (the SNC team) mistakenly targeted the wrong docker container, leading to exits from the Ethereal Elf cluster, where they are also one of the 7 participant Node Operators.

Double checking of the command by the Node Operator that the relevant command was directed to the correct container would have prevented this error, and documentation and instructions for cluster exits will be updated to guide such best practice behavior in the future.

An Easy Track motion will be started to increase the Ethereal Elf cluster’s key limit to 874 validators, utilising a portion of the 500 submitted but unconfirmed keys to bring the cluster’s depositable/active validator amount back to 500 total.

An update regarding the Majestic Moose cluster will be forthcoming after operations to reconstitute the cluster have been completed.

As there are only a limited number of SDVT depositable keys in the queue around this level, the Ethereal Elf cluster will be on-track to catch up to the other Super Clusters fairly quickly, and currently has 126 depositable keys.

Following this incident, a more detailed instruction guide will be added to the Simple DVT Portal providing specific step-by-step instructions in the event voluntary exits are required. Concurrently, the Obol Labs team will also review their current documentation regarding exits to add similar specificity.

Updates will follow in this thread with the Easy Track for Ethereal Elf and proposed cluster composition of Majestic Moose.

8 Likes
109

Yes, mistakes do happen - that’s part of the human factor, and no system is completely immune to it. But I genuinely believe that our instructions are written very clearly, and every step taken by an operator is double-checked multiple times. Only after full agreement is the next action executed.

At the cluster level, I think the workflows are very well organized. Of course, there are situations where operators may be unavailable or busy, but I know there are already measures being taken like hot-swaps and other fallback mechanisms to address such scenarios.

This incident is a strong reminder of why we verify even the most routine actions five to seven times. It may feel like a meaningless ritual sometimes, but it’s precisely this level of thoroughness that helps us avoid critical failures entirely.

I fully support strict regulation and precise adherence to instructions!

3 Likes
110

The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding one Lido x Obol Cohort 2 cluster: Lido x Obol: Majestic Moose.

One of the participants in this cluster, Yellowbee, has gone inactive and unresponsive over a period of multiple weeks. While the cluster continued to perform all duties successfully as the active number of nodes remained over the threshold, the cluster has since since performed a voluntary exit of their validators in order to replace the missing member.

After a discussion with the LNOSG to consider options, it was suggested to replace Yellowbee with Pacobits, another home staker that was previously proposed as a backup operator in the Obol Advanced Node Operator proposal. Pacobits would run infrastructure from the same geography, has shown strong mainnet performance, and is well known as an experienced Node Operator..

This rotation will allow for the cluster to move forward quickly to re-activate validators and move forward with its next steps.

The discussion period is now open for the DAO to consider these changes. Onboarding will begin optimistically however no keys will be submitted to the registry until the week discussion period is complete in the event additional discussion is required. The updated proposal is available to view here.

4 Likes
111

Summary

This update serves as the first performance report for the 10 Lido x Obol Cohort 3 clusters active on mainnet via the Simple DVT Module. Given overall solid performance results, it is proposed that the key limits for these clusters are raised to 80 validators, bringing them in-line with the remaining Lido x Obol clusters.

Performance Analysis

The performance monitoring period for Lido x Obol Cohort 3 began on March 26th, the day that all 10 clusters had active validators.

During this time, as per Rated, average uptime across clusters stands at 99.93%, aggregate Block Proposal Success Rate of 100%, and Average Validator Effectiveness is 96.96%. This compares to the 30 day overall Ethereum validator set performance with an average Validator Effectiveness of 96.63%. Initially, the Dynamic Dragonfly and Gallant Gecko clusters suffered from performance issues, though following troubleshooting with the Obol team the performance for these clusters has come back in-line with the remainder of the Cohort over the past two weeks.

For a detailed overview of cluster level metrics & the list of validator keys, see the analysis: Obol Cohort 3 Performance Metrics - Google Sheets

Proposed Next Steps

It is proposed that the key limits for Lido x Obol Cohort 3 clusters be raised to a maximum of 80 validators each, bringing the clusters in-line with the Obol Cohorts 2 & 3.

The relevant Easy Track motions for these key limit raises would be communicated in this thread and would follow the default approach of being veteoable by LDO holders over a 72 hour period.

This begins a discussion period for the DAO to consider the performance report and proposal to raise key limits to 80 validators for Obol Cohort 3.

5 Likes
112

An Easy Track is now live related to the participant replacement in the Majestic Moose cluster.

4 Likes
113

The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding two Lido x SSV clusters: Lido x SSV: Delightful Dolphin & Flirtatious Flamingo.

One of the participants in each of these clusters, DoraFactory & Lydia Labs, need to be replaced due to changes in the respective organizations’ operating structure. Both Node Operators have continued to run their nodes in the time between notification to Simple DVT Coordinators, in order to conclude testing of the SSV Network reshare functionality introducted in DKG v3.0. This testing was delayed due to the Holesky & Hoodi testnet situation, however following two successful tests on Hoodi, is now considered ready for mainnet. No cluster in Simple DVT is expected to participate in more than one re-share ceremony, meaning if further changes to these clusters are required, they will likely be exited and re-started with a new key limit.

After a discussion with the LNOSG to consider options, it was suggested to replace DoraFactory with IOnode, and to replace Flirtatious Flamingo with Girnaar Nodes, both operators that were previously proposed as a backup operators in the SSV Advanced Node Operator proposal
This rotation will allow for the cluster to move forward quickly while facing minimal interruption.

The discussion period is now open for the DAO to consider these changes. The updated proposal is available to view here.

5 Likes
114

Two new Easy Tracks are live:

  1. To increase the key limit for the Majestic Moose cluster following their cluster member replacement.
  2. To change the reward address for the Delightful Dolphin cluster following their cluster member replacement and reshare ceremony.
2 Likes
115

Another two Easy Tracks are now live:

  1. To increase the key limit for the Obol Cohort 3 clusters as noted in the performance report above.
  2. To change the reward address for the Flirtatious Flamingo cluster following their cluster member replacement and reshare ceremony.
5 Likes
116

The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding the Lido x SSV: Humble Hummingbird cluster.

One of the participants in this cluster, Vladcrypto, has dropped out and needs to be replaced. The operator has taken his node offline, and indicated he no longer wishes to participate in the module.

After a discussion with the LNOSG, it was suggested to replace Vladcrypto with Antotg, another home staker that was previously proposed as a backup operator in the SSV Advanced Node Operator (ANO) proposal. Anto would run infrastructure from the same geography, and has previously shown strong mainnet performance, while also being well known as an experienced Node Operator.
As the previous two SSV re-share ceremonies were successful, this rotation will take place in a similar fashion, allowing for the cluster to move forward quickly while facing minimal interruption.

The discussion period is now open for the DAO to consider these changes. The updated proposal is available to view here.

5 Likes
117

An Easy Track has now started to update the Reward Addresses for the 10 remaining SSV Cohort 1 clusters, available to view here, following the updates above of Flirtatious Flamingo and Delightful Dolphin.

3 Likes
118

Summary

This update serves as the first performance report for the 15 Lido x SSV Cohort 3 clusters active on mainnet via the Simple DVT Module. Given overall solid performance results, it is proposed that the key limits for these clusters are raised to 80 validators, bringing them in-line with the remaining Lido x SSV clusters.

Performance Analysis

The performance monitoring period for Lido x SSV Cohort 3 began on June 12th, the day that all 15 clusters had active validators.

During this time, as per Rated, average uptime across clusters stands at 99.88%, aggregate Block Proposal Success Rate of 100%, and Average Validator Effectiveness is 97.18%. This compares to the 30 day overall Ethereum validator set performance with an average Validator Effectiveness of 97.55%.

Initially, the Dashing Dingo, Vibrant Viperfish, Youthful Yellowtail and Xenial Xoloitzcuintli clusters suffered from performance issues, though following troubleshooting with the SSV team the performance for these clusters has come back in-line with the remainder of the Cohort over the past week. Furthermore, clusters Cheerful Cockatoo, Fearless Firefly and Zippy Zorilla are in the process of addressing their performance issues and are expected to show improvements in the near term.

For a detailed overview of cluster level metrics & the list of validator keys, see the analysis: SSV Cohort 3 Performance - Google Sheets

Proposed Next Steps

It is proposed that the key limits for Lido x SSV Cohort 3 clusters be raised to a maximum of 80 validators each, bringing the clusters in-line with the SSV Cohorts 1 & 2.

The relevant Easy Track motions for these key limit raises would be communicated in this thread and would follow the default approach of being vetoable by LDO holders over a 72 hour period.

This begins a discussion period for the DAO to consider the performance report and proposal to raise key limits to 80 validators for SSV Cohort 3.

7 Likes
119

The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding the Lido x SSV: Mysterious Manta cluster.

One of the participants in this cluster, HellmanResearch, has requested to wind down their SimpleDVT participation.

The discussion was opened with the LNOSG, and the suggestion is to replace HellmanResearch with Hayhouse Projects, another home staker that was previously proposed as a backup operator in the SSV Advanced Node Operator (ANO) proposal. Hayhouse Projects would run infrastructure from the same geography, and has previously shown strong mainnet performance, while also being well known as an experienced Node Operator.
As the previous SSV re-share ceremonies were successful, this rotation will take place in a similar fashion, allowing for the cluster to move forward quickly while facing minimal interruption.

The discussion period is now open for the DAO to consider these changes. The updated proposal is available to view here.

5 Likes
120

Just wondering, would it be possible to revisit the idea of adding more backup operators to the list? I know the current backups were set during the original ANO proposal? I noticed a few cases where backups were asked to step in. Might be worth considering an operator with a solid performance record but with little active validators until now. Could make things a bit more fair in terms of funding allocation across all operators.

2 Likes
121

@AXBLOX So far, we have not reached the point where the previously selected options have run out. Before that happens, the LNOSG will propose a new group to ensure there are enough operators ready to step in if needed.

Thanks for flagging this and for your suggestion.

4 Likes