[CLARIFICATION] Should DAO proposals have a pre-defined 'Abstain' voting option?
Proposal Details
Description
In the [enacted Governance proposal](https://governance.decentraland.org/proposal/?id=4ceeb900-ac83-11ed-ac8c-716656805a96) there are two definitions of how the Abstain votes behave when calculating the outcome of a proposal: In the Specification section, under the subtitle Implementation, I state: "The abstain option will be counted separately from the "for" and "against" votes, and will not affect the outcome of the vote." However, in the Implementation Pathway section I state: "If the 'Abstain' option accumulates more VP than the Yes/No option, the proposal will be considered 'Rejected' by the community." This mistake is simply a result of copying and pasting text from different versions of the drafts I used to elaborate the proposal. **The definition that should prevail is the one present in the Specification section: "The abstain option will be counted separately from the "for" and "against" votes, and will not affect the outcome of the vote."** This is how it currently works and it's how the Governance Squad implemented the feature in our Governance dApp and Snapshot strategy. Here's the [Github issue](https://github.com/decentraland/governance/issues/808) we used to track the development, where the task is specified.
0 Comments