Read the original proposal on Discourse
- Whitelisting proposals: 35% quorum, 66.7% supermajority.
- Co-investments < 1M BNT: 35% quorum, 66.7% supermajority.
- Co-investments > 1M BNT: 40% quorum, 66.7% supermajority.
- Liquidity mining: 35% quorum, 66.7% supermajority.
- Pool fees: 20%, 66.7% supermajority.
- Governance and protocol changes: 35% quorum, 66.7% supermajority.
*These are shown again under the FOR section.
The last proposals to whitelist tokens on snapshot have failed despite adequate engagement from voters. An improvement to the voting system is long overdue. Voting data on snapshot for all the wallets with vBNT currently staked in governance was collected [1]. With this data, an analysis of the current voter demographic was drawn to hopefully shed some light into the current voting issues to find adequate solutions for them.


Figure 1 - Active Voters and Voting participation
Supermajority Rule : Whitelisting proposals are still 40% Quorum but, having a supermajority of 80% (FOR) lowers it to 30% for whitelisting proposals. This will counter tactical voting since in order to beat the super majority they would have to vote against rather than abstain. 30% Seems like a good number because it is not incredibly easy to reach but in proposals like LPL the community, with the help of only a few mid-size whales, has been able to achieve it (The biggest one being xBNT which we can count on for consistent and reliable voting). This rule would essentially mean that overwhelming support for tokens will be treated differently than split decisions.
After some debate since it was posted, I believe most voters agree with @mbr 's thorough proposal.
1. All Whitelisting Proposals Include a Maximum 20k BNT Co-Investment, Subject to a 30% Quorum and 80% Supermajority Requirement.
There are good reasons for this. The lower quorum requirement makes it easier for an individual, or small group of individuals to pass a proposal. The system's vulnerability is increased, and the DAO needs to maintain its ability to manage pool sizes. It is not the case that a deliberate attack is necessarily the most pertinent threat - highly enthusiastic communities, and even our own community, can achieve the same damage without any nefarious intent. A hard limit of 20k co-invested BNT immediately following a whitelist proposal forces these new additions to be managed more carefully.
2. Co-investment Increases are Subject to Dynamic Quorum and Supermajority Requirements.
At present, co-investment increases are held to a 20% quorum and 66.7% supermajority requirement, regardless of the co-investment being requested. The low quorum is partly a reflection of the difficulty in whitelisting. If whitelisting pools is made easier, it stands to reason that increasing co-investment limits ought to be harder; the reduced barrier to entry must be commensurate with strengthened security later in the pool's lifecycle.
- Co-investment increases up to and including 100k BNT are subject to 30% quorum and 80% supermajority.
- Co-investment increases over 100k BNT are subject to 40% quorum and 66.7% supermajority.
3. Future Revisions to Whitelisting and Co-Investment Policy is Subject to a 30% Quorum and 80% Supermajority Requirement.
It is conspicuous that it is easier to change whitelisting policy, than passing a whitelist proposal. Strictly speaking, this is a type of governance hack. For example, consider that an antagonist who wishes to pass a toxic token has a reduced path to acceptance by first changing the whitelisting policy. This is not acceptable, and we have an opportunity here to close this apparent loophole.
I also want to address some of the user feedback, as well as the conversation that was hosted on our community call recently. We are absolutely committed to making Bancor the DAO to which all others are compared. This will require a comparable level of innovation as the product itself, and will be prioritized after the development pipeline is less congested. The main pain points are whale control and voter apathy - and I am working on a model to deal with both simultaneously. Rest assured that I