Support Required Deep Dive

What is the Support Required?

This is pretty straight forward…

Support Required is what percentage of tokens need to vote yes (of the tokens that were used to vote) for a proposal to pass in both Disputable Voting and Dandelion Voting.

Things worth mentioning:

  • Dandelion Voting and Disputable Voting use Token Weighted voting meaning its not 1 person - 1 vote.

  • A good range for Support Required is between 50-90%

  • Below 50% would mean a majority of voters could disagree with decision but it would still pass

  • Above 90% would mean a small minority of voters could block any decision from happening

So what do we need to decide?

  1. What information should we use to decide the Support Required?

  2. What is the benefit of a high Support Required (75%-90%)?

  3. What is the benefit of a low Support Required (50%-60%)?


NB: Supermajority is generally up to 75% rather than 90%, 90% is extreme. Although there’s the case of institutions requiring 100% support on some issues - a recipe for powerlessness, as evidenced by the EU (case in point: the current rescue package blocked by Poland and Hungary).

The tradeoff: use a simple majority in ordinary decisions, so that there’s the least possible friction in the normal course of affairs. Use supermajority for strategic decisions that require the largest consensus as it will bear long-term consequences on all stakeholders/members. If there’s no compelling reasons to add another threshold, it’s probably much better to have 2 levels max, it’s complicated enough.

Another way to approach supermajority is to do stakeholder groups. Simple majority within each stakeholder group is an elegant alternative to a higher support level. In traditional political institutions, it’s used when low and high chambers are required to jointly approved a decision, for instance. Same thing in the case of multi-stakeholder coops.

My 2 cents :slight_smile:


This is actually a really important point.

There are several parameters and permissions that can be changed and some of them are some what basic, while others are very critical.

We will probably want to have a few instances of Dandelion Voting with different Min Quorums and different Supports Required for the different levels of decisions.

1 Like

I think here is also important to know the level of commitment of the stakeholders. (whether they are also working in the projects or just voting and what % of the total supply they will own)
What i don’t know is why I think it is important :man_shrugging:t2:


What is the Support Required (%)?
The Support Required (%) is the percentage of YES votes from the vote-total required for a proposal to pass.

Implications & Parameter Options
The Support Required (%) is measured as a percentage (YES Votes/Total Votes), and you will have the option to set this parameter between 50 and 100.

The Support Required is an important consideration when developing responsible voting configurations. We desire consensus when voting, and the Support Required percentage is a direct reflection on the degree of consensus among token holders regarding any proposal. Consensus requires deliberation, and the parameters for the Commons Upgrade will be thoroughly debated. A high Support Required percentage means that a certain degree of consensus around the Commons Upgrade is required. A low Support Required percentage will allow for a small majority to dictate the parameters of the Commons Upgrade.

Suggested Range
Since support for a proposal is highly desirable, we suggest a range of 60%-95% for the Support Required parameter.

Related Parameters to consider when defining the Support Required (%):
Minimum Quorum (%)
Vote Duration (days)