As mentioned above, an Easy Track has now been started to raise the SSV Cohort 2 key limits to 20 validators. A subsequent motion is expected in the coming weeks to raise the limit to 40 as discussed in the SSV C2 Performance report.
1 Like
An Easy Track is live to raise the key limits of 8/10 of the Obol Cohort 3 clusters to their initial 5 validators. The Easy Track for the remaining two is expected to start next week after onboarding steps are completed.
2 Likes
The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding the results of the second SSV Simple DVT onboarding participant evaluations that took place on December 19th, 2024. This evaluation meeting followed the conclusion of the fourth Lido x SSV testnet, for participants to join the 3rd mainnet Lido x SSV Cohort.
If the proposal is accepted, the Simple DVT Module will consist of 72 normal clusters and 10 super clusters as laid out in the Simple DVT Module Proposal and Expansion proposal. In addition, the Simple DVT Module will have facilitated the addition of over 300 net-new Node Operators to the protocol, including over 180 solo and community stakers.
SSV Testnet Participant Evaluation
A total of 168 operators completed the fourth Lido x SSV Simple DVT testnet and were subsequently evaluated by the LNOSG. These participants were sorted into 24 clusters of 7 participants each, with various types of infrastructure configurations and geographic locations.
Evaluation Results
During the evaluation discussion, the LNOSG together with testnet coordinators from the Lido DAO NOM Workstream suggested 104 individual participants across 15 clusters with a 5/7 threshold configuration be onboarded to mainnet SSV clusters in the Simple DVT Module in the third cohort. As 21 normal SSV clusters are currently live on mainnet, a limited number of spots were available for participants to join with the expectation of 36 total clusters running in this configuration.
The proposed participants include a total of 66 net-new participants to mainnet Simple DVT, of which 37 are solo and community stakers. In some cases, participants with very strong performance that are already participating in Obol Mainnet Simple DVT Clusters were also proposed. In aggregate, a total of 47 solo and community stakers, 45 professionals, and 12 members of the Curated Node Operator set are proposed for onboarding in Cohort 3.
The candidates proposed by the LNOSG were considered to have shown strong performance, responsiveness, and reliability over the course of the fourth Lido x SSV testnet. These candidates utilize a diverse set of infrastructure hosting setups including on-premise, bare metal in a datacenter, and public cloud, and support a wide range of EL & CL clients.
The compositions of the 15 proposed clusters are designed to minimize latency and support infrastructure diversity. Additionally, all clusters have participants that support a range of EL & CL clients.
The proposed participants have been asked to confirm their desire to join the Simple DVT Operator Set via an SSV cluster. In case they do not reply affirmatively in a timely manner, or for some other reason cannot participate, the LNOSG will make an adjustment to the proposed list and share an update in this thread.
During the final meeting on December 19th, 2024, the LNOSG suggested to propose the following SSV based clusters for inclusion into the Lido Simple DVT Module Ethereum protocol:
Proposed Lido x SSV SDVT Clusters - Google Sheets
You can find the full PDF with summary statistics and the LNOSG meeting recordings of the introduction and final conclusion of the cluster proposal in the public drive below. Due to the privileged/confidential nature of some of the information provided in some of the applications, the portion of the call where applications were discussed in detail was not recorded.
https://drive.google.com/drive/folders/1F71df9238XCTy_pg0f2a33F1PXpMTMQr
All participants in the testnet have been emailed notifying them of the results and are welcome to reach out via email to [email protected] for further clarification.
Path to Mainnet
DAO Discussion Period
A 7 day discussion period is now open for the DAO to discuss the proposed participants for the Cohort 3 SSV clusters within the Simple DVT module.
Should the DAO disagree with any of the proposed applicants, request additional information, or otherwise request additional input for the onboarding, the LNOSG will reconvene to propose a next course of action.
If after 7 days, no major changes are required by the DAO, the Simple DVT coordinators from the Lido DAO NOM Workstream and SSV Labs will begin the coordination process with cluster participants.
Next Steps
If no adjustments are required after the week discussion period, the SSV clusters will be added to coordination threads and begin the process of verifying addresses and setting up cluster multisigs. The Lido Simple DVT Module Committee will create their entries in the Simple DVT Node Operator Registry via Easy Track and notice will be provided in this thread.
7 Likes
We (NodeSoda) are honored and glad to be short listed to join the DVT community. We look forward to actively participating and contributing to Lido.
5 Likes
ContributionDAO is deeply honored to be shortlisted for Cohort 3. We are fully ready to participate wholeheartedly.
4 Likes
We at AXBLOX are excited to be shortlisted for Cohort 3 and look forward to collaborating with the DVT community. We’re committed to actively participating and contributing to the growth and success of Lido.
4 Likes
Thank you for choosing DeeNode to join your project. We are happy to join the Lido Simple DVT Module operator using SSV.
4 Likes
An Easy Track motion is now live to increase the key limits of the five SSV Super Clusters to 500 validators, following the steps outlined in the performance report above.
1 Like
An Easy Track is now live for the remaining two Obol Cohort 3 clusters to raise their key limits to 5 validators.
Nothing to for the SSV#4 testers here correct?
Pier Two is excited to be shortlisted to participate in Cohort 3. The team remains committed to seeing DVT and Lido continue to succeed in securely staking.
3 Likes
Nothing yet, we will add everyone to Discord threads by Monday at the latest and next steps will be shared there.
2 Likes
Chianlabo is honored to be part of Cohort 3 and can’t wait to move on to the next phase
3 Likes
Tranquil Turtle Incident Report - 26/1/25
On January 26th, it came to the attention of SDVT coordinators that CryptoZab from the SDVT Tranquil Turtle Obol cluster has some addresses compromised (the Individual Manager & Reward address) as a result of the AdsPower Browser exploit. This is an address related to cluster participation and receipt of rewards, and is not attached to any kinds of validator operations.
Validator operations were not directly impacted as a result of the exploit and no staker funds are at risk as a result of this instance of address compromise.
Notice was brought to the Simple DVT Module Committee, which created an Easy Track motion setting validator key limits for the Tranquil Turtle cluster to 0.
Concurrently, Node Operators within the Tranquil Turtle cluster coordinated to utilize voluntary exits to trigger exits for the cluster’s 60 active validators. All 60 validators are in the process of exiting at this time and the impacted address has been rotated out of the cluster multisig.
Coordinators are in the process of communicating with all Simple DVT participants to understand which, if any, other Node Operators may also have addresses compromised as a result of the exploit. At this point, no further impact has been identified however follow up is expected to be ongoing over the coming days.
While the scope of the exploit is still under investigation by the AdsPower & Slowmist teams, as the cluster’s validator keys were generated via Obol’s Distributed Key Generation mechanism, the affected address compromised as a result of the AdsPower exploit has no effect on the validator keys (or the participant’s key shard).
A more detailed incident report will be published in this thread in the coming days with an update regarding any other potential impacted clusters and to discuss next steps for the Tranquil Turtle cluster.
11 Likes
Hello everyone, following up on the previous notice to let everyone know that the version v3.0.1 of the ssv-dkg tool has been publicly released.
v3.0.1 release, what has changed?
As previously mentioned, the previous version (v3.0.0) has undergone an official audit. The core functionalities are unchanged and untouched in v3.0.1, the only items in the changelog only impact the user experience, and cover an edge case of the reshare functionality. Here they are:
- fix of the automated certificate creation in the docker image entry point
- fix of a command line parameter to provide the proofs file as a path (providing file content as a string has always worked)
- stopped exchanging messages with old inactive operators in case of
reshare
You can verify them on the release page itself on GitHub.
SSV WebApp
The SSV WebApp has also been updated accordingly, to provide guided procedures to regenerate keyshares with the newest DKG tool release.
It is now able to detect if a user’s DKG endpoint is reachable (as it had so far), and if such DKG server is “reshare capable” (if the version is v3.0.1) and if it has the capacity of verifying multi-sig signatures (the DKG tool needs to have an Execution layer RPC endpoint enabled).
Please follow our updated guide to update your operator’s DKG node.
I remain available for clarifications an questions you might have.
4 Likes
Follow up to Tranquil Turtle Incident Report
As mentioned above, on January 26th, it came to the attention of SDVT coordinators that CryptoZab from the SDVT Tranquil Turtle Obol cluster had an address compromised (one address acting as his Individual Manager & Reward address) as a result of the AdsPower Browser exploit.
Cluster participants in the Tranquil Turtle cluster coordinated to utilize voluntary exits to trigger exits for the cluster’s 60 active validators, all of which have now fully exited.
In parallel, Lido DAO contributors conducted an analysis of the addresses tied to the exploiter and compared them to the Individual Manager & Reward Addresses of all participants in Simple DVT. No other Simple DVT addresses were identified as being impacted by the exploit. In addition, 255/261 active Simple DVT participants have now confirmed via manual verification that their addresses were not compromised and, if they were using the browser, confirmed they had not used it with their Simple DVT related addresses.
Of the 6 remaining participants surveyed, one participant, Highnok (member the Lido x Obol Majestic Moose Cluster) had utilized the AdsPower browser with a SDVT address, though was not impacted due to disabling automatic browser plugin updates. However, the decision was made by the cluster to change Highnok’s address in the cluster multi-signature wallet and rewards splitter out of an abundance of caution. The address change is reflected here & the Easy Track motion is pending here. The other 5 are still pending manual verification.
Tranquil Turtle Update
Following the incident, a discussion was opened with the cluster participants and the Lido Node Operator Subgovernance Group about whether CryptoZab should continue to participate as a member of the Tranquil Turtle cluster. The 6 other cluster participants and LNOSG overwhelmingly agreed that CryptoZab should continue to participate as a member of the cluster, taking greater care to limit exposure of his Simple DVT addresses and to use a hardware wallet.
As a result, an Easy Track is expected this week to re-create the rewards splitter contracts for Tranquil Turtle, and the cluster will coordinate to add CryptoZab’s new address to the multisig and reform the cluster via DKG.
Conclusion
The Tranquil Turtle Cluster will be reformed with the new address included over the next few days, and the Majestic Moose cluster’s validators will continue to operate without impact.
It is worth noting a special thanks to the Obol Labs team for assisting with troubleshooting during the exit process and incident follow up.
2 Likes
Summary
This update serves as the second performance report for the 9 Lido x SSV Cohort 2 clusters active on mainnet via the Simple DVT Module. Given overall strong performance results, it is proposed that the key limits for SSV Cohort 2 are raised to 80 validators in a phased approach, with the exception of the Quiet Quetzal cluster that will remain with a maximum 20 keys.
Performance Analysis
The performance monitoring period for Lido x SSV Cohort 2 began on Oct 18th, the day that all 9 clusters had active validators.
During this time, as per Rated, average uptime across clusters stands at 99.93%, aggregate Block Proposal Success Rate of 94.74%, and Average Validator Effectiveness is 96.94%. This compares to the 30 day overall Ethereum validator set performance with an average Validator Effectiveness of 97.25%. All of these metrics have increased since the initial performance report. Excluding the Quiet Quetzal cluster, Average Validator Effectiveness was 97.87%, though this cluster does continue to have a 100% Block Proposal Success Rate.
The SSV team is continuing the troubleshooting process with cluster participants in the Quiet Quetzal cluster. While metrics have improved since the last performance report (e.g. Validator Effectiveness increase of 4.61% points), performance still has room to improve. It is proposed Quiet Quetzal remains at a 20 validator key limit until metrics are observed in the next performance report.
For a detailed overview of cluster level metrics & the list of validator keys, see the analysis: SSV Cohort 2 Performance Metrics - Google Sheets
Proposed Next Steps
It is proposed that the key limits for Lido x SSV Cohort 2 clusters be raised to a maximum of 80 validators each until the next performance monitoring period (which will end no earlier than 37 days after the publication date of this update), in a phased approach of raising the key limits to 40, followed by an additional raise to 80 after the initial 35 additional keys have been deposited to and observed to activate without issues.
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 key limits to 80 validators in a phased approach for SSV Cohort 2, excluding Quiet Quetzal at a maximum of 20 validator keys.
5 Likes
The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding one Lido x SSV Cohort 3 cluster: Lido x SSV: Agile Aye-Aye.
The participant, Jirzy, has decided to not move forward in onboarding via Lido x SSV Cohort 3.
After discussion with the LNOSG, it was suggested to replace Jirzy with 2xStake, another Community Staker that was previously proposed as a backup operator in the SSV Super Cluster proposal. 2xStake would run infrastructure from the same geography, has experience as a Cluster Coordinator, and voluntarily participated in the last SSV testnet to assist new participants.
This rotation will allow for the cluster to move forward quickly with onboarding.
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.
3 Likes
The NOM contributor workstream on behalf of the Lido Node Operator Subgovernance Group (LNOSG) would like to provide an update regarding one Lido x SSV Cohort 3 cluster: Lido x SSV: Insightful Ibex.
One of the participants, Everstake, has decided to not move forward in onboarding via Lido x SSV Cohort 3.
After a discussion with the LNOSG to consider options, it was suggested to replace Everstake with Openbitlab, another Professional Node Operator that was previously proposed as a backup operator in the SSV Advanced Node Operator proposal. Openbitlab would run infrastructure from the same geography, has shown strong mainnet performance, and voluntarily participated in the last SSV testnet to assist new participants.
This rotation will allow for the cluster to move forward quickly with onboarding and moving 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.
2 Likes
Summary
This update serves as the second performance report for the Vivacious Viper Lido x Obol Cohort 2 cluster. As mentioned here, there was a late replacement for this cluster that resulted in the participants having to restart the setup process.
Given very strong performance results, it is proposed that the key limits for Vivacious Viper are increased to 80 validators.
Performance Analysis
The first performance monitoring period began on October 1st. Since that time, as per Rated, uptime for the cluster was 99.95%, Block Proposal Success Rate of 100% (17/17 proposals), and Average Validator Effectiveness was 97.92%. This compares to the 30 day overall Ethereum validator set performance with an average Validator Effectiveness of 96.79%.
For a detailed overview of cluster level metrics & the list of validator keys for all of Cohort 2, see the analysis: Obol Cohort 2 Performance Metrics - Google Sheets
Proposed Next Steps
It is proposed that the key limits for the Vivacious Viper cluster is increased to 80 validators given the very strong results, in-line with the rest of Obol Cohort 2.
The relevant Easy Track motions for this key limit raise will 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 the Vivacious Viper cluster.
1 Like