Conviction Voting Contests / Prioritizing Ideas with CV

[sembrestels]

In order to use Conviction Voting to decide the winner of a contest (or the top 3 current priorities of a Community), it doesn't have sense to have a threshold and a money allocation for the first proposal that passes it. We only need to watch how community conviction increases and decreases over time and make collective decisions based on it.

Installing a conviction voting app without a funding pool should result in a frontend without threshold, beneficiary, nor funding requested.

Conviction without money allocation #33

In this use case it may also be interesting for communities to signal many applications / ideas at the same time. We can give splitting the vote an advantage by applying quadratic voting to the tokens people stake.

Allow users split their stake tokens among multiple proposals #36

Quadratic Conviction Voting #37

Finally, in order to foster collaboration among people and combine and improve ideas, we introduce the concept of nested proposals.

A nested proposal is a "fork", an alternative proposal that is built on top of a previous proposal. When supporting a nested proposal, you are supporting also the parent one, and we can have various levels, so we end up having a tree of proposals. This system allows people to tweak proposals and seek support without the risk of losing conviction in between. Nested proposals compete among their siblings, but the top proposal still receives all the conviction deposited in them.

Nested proposals #38

We can use this system to prioritize 1Hive ideas, or organize a Solarpunk literary contest (very, very cool, guys).

[GriffGreen]

playing devils advocate... is CV the best governance solution for discrete events like deciding a winner of a contest"?

Has there been much visioning on the best use cases of CV?

I can start a little...

CV was designed specifically for allocating a scarce shared resources across multiple competing proposals.

It assume a continuous voting period and proposal period and that there is an organic discovery process such that if new good ideas appear people will be notified and people can change their stance.

1. I think signalling a communities' top 3 priorities is a good application... the scarse resource being attention and and if new ideas can come up over time.. but there will have to be some games being played with the threshold formula. :-D as talked about in Allocations: Conviction Voting #33... I think this one should have a more concrete use case and be played with... Issue prioritization in github was played with by Pavle, Sponnet, Kay and Loredona at ETHParis: https://github.com/gitviction/gitfyah

2. Funds in a dao to multiple proposals (easy win)

3. A liquid democracy style conviction may be interesting.... it might align incentives better and produce better results than a discrete shift of voting power. I actually REALLY like this idea....

4. Could CV be integrated into a TCR style ordering of a list sort of similar to Documentation Hub #1 but imagine a TCR for best mexican restaurant where every time you eat at a mexican restaurant you get a token... I dont really like this application the more i think about it... because a restaurant that was great for a year but then the good chef left, there would be a lingering high score... SO this says that when there are discrete events that can drastically change people's preference, a CV approach may not be best.

5. commonly occurring group choices like where should we go to lunch today. other rules can be put in place like... when a choice wins it is taken off the list for some days...

There are probably a lot more...