KVORUM
lidoSource: Snapshot · #0x1ebfab7522c427e2a2a188340cf5f995982e277e892d7b50be07bc8ab9d1b37f

Vote on 'Two-phase voting' proposal for Lido DAO

succeededJun 13, 2022, 11:00 AM UTCsignaling · non-bindingbyAE0xaea2…56c7View on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

147 words

Lido dev team recently shared their thoughts on 'last moment vote' attack mitigation (see the "Discussion" link).

The proposal is to split each Aragon vote timeframe into two phases while maintaining the overall vote time to be 72h:

  • Main, where one can vote both for and against — 48h
  • Objection, where one is only allowed to vote against — 24h

Which allows:

  • to prevent unexpected changed from being propagated in the last moment
  • to have a 24h period to react before the vote decision comes into force

You can find more details in: LIP-16 - Protocol safeguards. Two-phased voting

The changes are implemented with the following PR in the Lido fork of aragon-apps repository: https://github.com/lidofinance/aragon-apps/pull/8

The on-chain code is peer-reviewed internally and audited by the MixBytes team.

Do you support the proposed 'Two-phase voting' to be implemented as Lido DAO Aragon Voting upgrade?

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.