• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
LidoLidoby0xAeA283989e4960070913e3d87c5419c545fF56C7folkyatina.eth

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

Voting ended over 3 years agoSucceeded

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?

Off-Chain Vote

Yes
60.76M LDO100%
No
1.33K LDO0%
Download mobile app to vote

Discussion

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

Timeline

Jun 07, 2022Proposal created
Jun 07, 2022Proposal vote started
Jun 13, 2022Proposal vote ended
Oct 26, 2023Proposal updated