KVORUM
lidoSource: Snapshot · #QmRhYv5UL4tFbLzbrhn9UEEeHDoFenurv1BG1cKgJfrhLd

Re: Should Lido use third party cover providers?

succeededJul 17, 2021, 11:00 AM UTCsignaling · non-bindingby000x0044…0fbcView on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

188 words

Starting another snapshot vote on the cover, as we need to have the quorum for the question. The previous one concluded mostly in favor of "don't renew the cover, explore self-cover", but only ~2.1% of the total votes have been cast.

Currently Lido has cover for 5% slashing penalties on ~90% of each operator's stake (every operator has slightly different numbers here). The cover was bought from the dev team funds for ~66.3 ETH.

As discussed in the forum, Lido should make a decision around its next steps on cover.

This poll's purpose is for token holders to signal how they think Lido should move forward with the cover paths as mentioned in the post.

Depending on the outcome, a follow-up vote may occur for deciding the implementation path.

Snapshot does not allow longer-form text in the poll choices so expanding here for clarity:

  1. Renew Cover: Re-purchase cover from Unslashed Finance
  2. Do not renew cover: Do not re-purchase cover from Unslashed Finance
  3. Do not renew cover and explore self-cover: Do not re-purchase cover from Unslashed Finance and explore self-cover (mechanism TBD given multiple potential avenues)

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

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.