Ah true. My concern is that setting this figure at a nominal or % basis will mean a consistent failure to pass quorum; eventually, if not immediately. The data in the first image suggests this if we go with the proposed 30%.
I’ve suggested a solution. Basically an ASR qualification based on Participation % against number Total # of Proposals.
This incentivizes participation and would mitigate against the risk of quorum failure.
My fear is that setting this figure at a nominal or % basis will mean a consistent failure to pass quorum; eventually, if not immediately. The data in the first image suggests this if we go with the proposed 30%.
I’ve suggested a solution. Basically an ASR qualification based on Participation % against number Total # of Proposals.
This incentivizes participation and would mitigate against the risk of quorum failure.
If Quorum % continues to decline, then the DAO risks a failure of the voting process.
This could be mitigated by implementing a requirement for users to participate in governance; a quorum of x % participation of all Proposals.
Bob never votes. He has not reached quorum to receive ASR.
Bob is now incentized to Vote, or Reduce Stake.
This works to ensure a successful Quorum for each proposal.
My mitigation solution is three fold. Essentially I’m saying to qualify ASR Rewards to only those wallets who achieve a certain % of Voting Participation. Then include % quorum to pass a vote, as the proposal offers. This does three things:
Ensures Voters are incentivized to participate in the DAO
Mitigates risk of Quorum failure (repeat failure)
Increases rewards APR for active Voters
We should VOTE NO on this proposal and produce a new one with the amendments.
I think the last vote is pointless, because you will always get 100% success as long as you incentivize with rewards and as long as the changes are submitted to the vote by team members, not by people. On the other hand, you could make not a threshold for voting, but a threshold for agreeing or disagreeing (First, a vote for accepting the topic for voting, and if the threshold is passed, then a vote on the topic.) by several metrics:
number of voting wallets
number of JUP
number of months of active participation in the project * JUP = voting power in JUP
as far as I know, these statistics can be collected, and then figure out how to create a coefficient for accepting a vote
Think higher than 30% to offset any outsized power held by large accounts. Realistically, to better represent the entire population, we would need to introduce some additional logic to cover nuance. Wallet address count should be factored in at least.
I think the best is 30% because the fluctuation of staking don’t interfere. In the other case we have to update at each time of fluctuation with another vote
why aren’t you requiring a higher percentage of staked JUP than 30%? It seems so low. In my mind quorum should be a metric to engage leadership, not the community. If you set the level higher it forces leadership to keep engagement higher in order to keep votes moving along.
I’m in favour of the percentage over a set limit. It’s more flexible and reflects the focus on the staked JUP itself. In the future it might be you want a lower/higher rate of staking so the threshold should move with that.
Everyone seems to be in favor of Increasing this number as its reasons are pretty clear. I do think that revisiting this Topic multiple times is overkill and think we could “as they say” kill 2 birds with 1 stone and vote for 30% active stake, Or in my opinion maybe 36%+