Voting Concept: 2-Factor Majority

[worza]

This system can also be used with my other suggestion for ‘multiple-choice selection’ with custom voting power allocation.

Bracket Based Voting Proposal

I do like the approach and how further rounds earn more exposure with introducing the project. But there are a few complications that we would need to consider; As @yellowdino pointed out here - This is a valid point and even if you go with @Cortezz suggestion for a double elimination bracket, what we have then is another problem with a flood of voting frequency that will backlog or require change to the queue and execution times. In short – this will create voting congestion as what would …

So here you would use fractal/decimal to tally up the ‘Voter’ count that is separate from the JUP weighting.

E.g. distributing voting power like such;

Your Total VP: 1000

(select one or multiple).
Project A. - 30% of VP (300 JUP)
Project B. - 20% of VP (200 JUP)
Project C - 15% of VP (150 JUP)
Project D - 35% of VP (350 JUP)

Each would tally as 0.25 for the ‘Voter’ count, more specifically being 1 divided by how many choices you select.

Other examples;

(select one or multiple).
Project A. - 30% of VP (300 JUP) Counts as 0.33 Voter Tally
Project B. - 20% of VP (200 JUP) Counts as 0.33 Voter Tally
Project C - 50% of VP (500 JUP) Counts as 0.33 Voter Tally
Project D - 0% of VP (0 JUP)

(select one or multiple).
Project A. - 30% of VP (300 JUP) Counts as 0.5 Voter Tally
Project B. - 70% of VP (700 JUP) Counts as 0.5 Voter Tally
Project C - 0% of VP (0 JUP)
Project D - 0% of VP (0 JUP)

In this way we can solve the ‘bribe/perks’ offerings for exclusive voting, as all can easily qualify with minor voting power allocation to each candidates. And you can still maintain the benefits of the 2-factor majority system with improved consensus.