KVORUM
lidoSource: Snapshot · #0x85ebbe2cb80334c60e160ff267118489e17281046757561e91c5b22dae35e577

Should the Lido DAO add the 2 shortlisted Ethereum operators to the Lido on Ethereum operator set?

succeededJul 27, 2023, 06:00 PM UTCsignaling · non-bindingby470x479f…a82aView on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

256 words

Summary

This proposal is to onboard new node operators to the Lido on Ethereum Node Operator Set.

Proposal

The goal of onboarding new node operators is to improve the decentralization and resilience of the Lido protocol, as well as to bring on new organizations with strong skill sets and alignment with Lido’s values.

The onboarding round is occurring in two stages.

In Stage 1, the Lido Node Operator Sub-governance Group (LNOSG) reviewed and evaluated 14 onboarding applications, resulting in two applicants proposed for the Stage 1 shortlist for onboarding onto Lido on Ethereum.

The Stage 2 evaluation and subsequent shortlist proposal are tentatively planned for the end of August/early September when additional candidates for inclusion will be proposed.

The two shortlisted candidates proposed by the LNOSG were deemed to appropriately reflect the onboarding goals outlined in the Lido Operator Set Strategy and the “Factors to Consider'' section of the onboarding announcement.

Following a meeting on July 11, 2023, the LNOSG recommended the following applicants for inclusion into the node operator set for the Ethereum protocol (in alphabetical order):

Next steps

This vote will run for seven days and seeks LDO holder approval of the onboarding of the above-mentioned node operators for the respective protocol, provided the operators confirm their desire to join.

In case the Snapshot concludes in favor of onboarding, the Aragon vote will follow to add node operators accordingly.

For more information, please see the relevant onboarding announcement and evaluation results posted on our forums.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters366
VP participating0
Outcome (current)For
Current support100%

06Voters

366 total
Filter:
VoterChoice% of totalRationale
B80xb842…82b0For037.08%—3y ago
4A0x4af8…6a0bFor022.44%—3y ago
D10xd1c7…0aaeFor015.98%—3y ago
510x510a…8d0eFor07.53%—3y ago
6D0x6d8d…0cccFor06.18%—3y ago
6A0x6a39…4bd2For05.53%—3y ago
A20xa2ff…7be9For01.65%—3y ago
FE0xfe45…2e4bFor01.09%—3y ago
E80xe80e…28e8For00.75%—3y ago
110x116a…41b9For00.48%—3y ago
340x3437…5c16For00.41%—3y ago
C20xc2e0…d399For00.33%—3y ago
660x666f…21fcFor00.26%—3y ago
780x78d1…753aFor00.11%—3y ago
BC0xbce3…776fFor00.07%—3y ago
3E0x3ec6…cb63For00.06%—3y ago
490x49f1…6cdbFor00.03%—3y ago
B00xb0fd…9ca7For00.00%—3y ago
470x479f…a82aFor00.00%—3y ago
3D0x3d5a…b97fFor00.00%—3y ago
A50xa575…f6e8For00.00%—3y ago
760x76a9…94d0For00.00%—3y ago
8D0x8d07…a265For00.00%—3y ago
3C0x3cf0…3256For00.00%—3y ago
D90xd929…b62cFor00.00%—3y ago
530x53a0…3dd4Against00.00%—3y ago
B40xb4dc…7e9aFor00.00%—3y ago
910x9109…43a3For00.00%—3y ago
550x55c5…7bccFor00.00%—3y ago
EA0xea17…6676For00.00%—3y ago
CF0xcf2b…e05dFor00.00%—3y ago
520x5259…f0cfFor00.00%—3y ago
AA0xaa61…7d71For00.00%—3y ago
000x0099…8147For00.00%—3y ago
520x5243…3440For00.00%—3y ago
C30xc34a…68c2For00.00%—3y ago
F40xf4dd…c29eFor00.00%—3y ago
2E0x2e07…5399For00.00%—3y ago
A40xa4eb…31afAgainst00.00%—3y ago
9F0x9fc7…20d7For00.00%—3y ago
CF0xcf56…e8d7For00.00%—3y ago
A60xa697…261cFor00.00%—3y ago
B70xb7a3…abc9For00.00%—3y ago
B70xb729…01fbFor00.00%—3y ago
380x38fe…59f0For00.00%—3y ago
8E0x8eec…b111For00.00%—3y ago
740x74ec…c176For00.00%—3y ago
140x14bd…e36aFor00.00%—3y ago
5E0x5ef8…c747For00.00%—3y ago
D30xd31a…1072For00.00%—3y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.