Goal is to make the protocol configuration propositions to be voted and accepted in a more fair way. The proposal is to create an ACP (Airwap Configuration Proposal) voting system that will help to vote for changing of Smart Contracts configurations like SCALE, MAX, throttlingPercentage, throttlingDuration, throttlingBalance etc. in the same way as we vote for AIPs. A correct implementation should result in a fair voting considering each staker vote power and rise the turnout.
Also each configuration change should stay same for a minimum of 2 voting cycles before it can be changed again.
The ACP voting proposals may be added to the same page near all other AIPs on Activate Governance page “clickable link”
The vote mechanics should be the same as for AIP voting with one change: as those votes may be not structured in time and can be voted more often that usual AIPs the points scoring amount received for this voting should be reduced to 0.
Protocol configuration changes are no less valuable as any other AIP and should be voted in the same mechanics as usual AIPs.
We can also attract new voters because according to the last SCALE and MAX rates change vote we had only 11 votes total, which is quite low turnout. Also 100k staker vote should not have the same weight as 10k staker vote like we saw in Discord during the “smiles voting”.
- Low turnout
- Unequal vote weight relative to the stake in the project
Thanks to BeDreamin83 for their contributions to this AIP
Copyright — All proposals are public domain via CC0.