Title: eIP 43 : Allow “abstain” vote
Authors: @knightsemplar / @Raslambek
Submission Date: 13/01/23
Summary
The current vote contract is configured to only allow “yes” or “no” votes.
An “abstain” option should be added.
Motivation
As the DAO is developing, there has appeared a request from the community to introduce an “Abstain” option. This includes but not limited to:
- eIP 18: Move all asset price oracles to Chainlink where available ahead of the Merge
- eIP 38 Delegate Optimisations in Governance: 2 - Recognised Delegates
- @0xBaer suggested it in his [Ideation] Formulating the Proposal Lifecycle
- Daostewards explained why they decide to abstain for the Encode Grant Proposal
It is also natural, that with eIP 38 close to approval and the Recognised Delegates programme launched, RDs will face a conflict of interest when filtering and voting for the next batch of RDs. The potential risk is that RDs will vote for themselves or those who they filtered.
At the same time, given the commitment to take part in >80% of all votes, Recognised and Active Delegates are not in a position to express their abstention by not participation in the voting. In this regard, “abstention” would be a way out to both maintain high level of participation and avoid conflict of interest.
In order to avoid gamification of the Governance by using “abstain” to maintain high participation level in the voting without meaningful contribution to the discussion and decision making process, the “abstain” vote should be properly explained both on the forum and Snaphot in respect of a particular proposal
Specification & Implementation
The Euler Foundation would be engaged to change the voting contract to allow for “abstain” as an additional voting option.
Voting
- Yes, implement this change.
- No, leave things as they are.