# The newest proposal for Lido DAO

By [PCPOP'S HOME](https://paragraph.com/@pcpop) · 2022-06-12

---

[https://snapshot.org/#/lido-snapshot.eth/proposal/0x1ebfab7522c427e2a2a188340cf5f995982e277e892d7b50be07bc8ab9d1b37f](https://snapshot.org/#/lido-snapshot.eth/proposal/0x1ebfab7522c427e2a2a188340cf5f995982e277e892d7b50be07bc8ab9d1b37f)

Lido dev team recently shared their thoughts on 'last moment vote' attack mitigation (see [the "Discussion" link](https://research.lido.fi/t/proposal-last-minute-vote-mitigation/2162)).

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](https://github.com/lidofinance/lido-improvement-proposals/blob/two-phase-voting/LIPS/lip-16.md)

The changes are implemented with the following PR in the Lido fork of aragon-apps repository: [https://github.com/lidofinance/aragon-apps/pull/8](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?**

---

*Originally published on [PCPOP'S HOME](https://paragraph.com/@pcpop/the-newest-proposal-for-lido-dao)*