Number of Dandelion Voting Instances

What is a Dandelion Voting Instance?

A Dandelion Voting Instance is a subset of apps within Aragon’s Dandelion deployment specific to voting. Each Voting Instance will have it’s own set of parameters. Parameters such as the Support Required, Min Quorum Required, Vote Duration, Vote Proposal Buffer, etc.

Votes to change specific permissions will be linked to one Voting Instance, determining the set of parameters required for that vote to pass.

What is important to consider?

Here, it is important to consider how simple or how complicated we require this to be. With just one Voting Instance, the single set of parameters will apply to all votes. Multiple Voting Instances allow more flexibility to increase the Min Quorum Required and Support Required for votes that have higher impact on the system and future of the DAO. Too many Voting Instances may cause confusion for participants on the voting rules and how and when they are applied.

As an example, high impact votes may include the parameters of Augmented Bonding Curve (ex. pausing the bonding curve), parameters of Conviction Voting, adding a new app or upgrading the DAO to include the ABC and CV in the first place.

So what do we need to talk about in this forum post?

  1. What information should we use to decide how many Voting Instances we should have?
  2. What permissions and parameters should be considered low or high impact?
  3. How else should we look at grouping permission to a Voting Instance?

Hey!! I’ve been thinking about this, mostly because of the ability it gives us to have multiple min support required, vote durations and min quorum required.

it kinda seems logical that some votes that need a high support and high quorum required probably need also a long voting duration (for the most important decisions)

it also seems logical (or not?) that votes that need a low support and low quorum required, probably need a short voting duration (for lightweight decisions)
what I would like to find out is a scenario where either it’s needed:

  • a low support, low quorum required and a long voting duration
  • a high support, high quorum required and a short voting duration

I’m also wondering whether it’s correct that support required and quorum required go tightly correlated or maybe it’s just enough for example with a high quorum required to do the job for the most important decisions

1 Like

In the case of having 2 or 3 instances, who decides what goes on each instance?
If the one making the voting decides, then, what/who would stop him/her from choosing conveniently to his/her own preferences?
Should there be a vote for deciding which voting instance should be used for the vote? (Nested voting)

“There will be one Dandelion DAO that can set permissions for things that are F*KN crazy.” -Griff (God mode)

One Dandelion DAO will rule them all and be able to set permissions for other Dandelion DAOs <- (Is this true, or are DD permissions fixed from the beginning?)

My intuition on this is telling me that we need AT LEAST 2, but we don’t want too many, so it seems like 2-5 is a kind of sweet spot.

I think that the fundamental first step is to list out all the permissions, otherwise how could we possibly know how many groups of permissions we need? Can anyone help with listing all permissions? @sem @Griff you know a good place to look for this?

1 Like

A high support high quorum low duration would be to take a drastic action in impending disaster.

Low support low quorum long duration might be planning a low cost fall project while it’s still spring.

I think I’m understanding the question correctly.


From Flare: