This AIP proposes to implement a regular schedule for voting on AIPs. This will give enough time for AIPs to be discussed and fleshed out before they go up for voting. Furthermore, it will give time for developers to work on implementation of the AIP.
In the current implementation, there is no fixed schedule for when AIPs get called to vote. This creates two problems:
- Stakers are unsure of when to participate in votes and results in uncertainty of when to claim
- AIP authors and developers may not get sufficient time to work on / implement current ideas. For example, a proposed implementation for one AIP may change the technical implementation of a different AIP. It would be better for the specification of multiple AIPs to be worked on concurrently.
- AIPs will be called to vote every 3 weeks.
- First cycle begins Thursday, April 15th with the first vote on the same day.
- Each vote starts at 9am Eastern Time and runs for 4 days (96 hours).
- AIPs to be called to vote will be announced at least 2 weeks before the vote in order for the community to discuss the details and to give time for the author(s) to make relevant changes before the AIP is voted on. This should include details about the required implementation budget (with the help of the project team)
- Several AIPs will be voted on concurrently each cycle and at the end of the voting period, the project team will then queue accepted proposals for implementation.
- Participating in a cycle earns 1 point per AST staked by the voter. Points are earned proportional to the number of votes participated in for the cycle e.g. if there are 2 votes, participating in one earns half of the full reward, participating in both earns the full reward.
- If no AIPs are ready in the current cycle, a “roll-call” vote will be called to update voters about the current status of the project. This ensures that the community stays up to date and stay confident that the project is still running smoothly.
Rewarding points per cycle might seem like a reduction in the number of total points distributed as compared to rewarding points per vote. However, it should be noted that the rate of points distribution will not change compared to the current implementation (to date it has always been one vote at a time)
A fixed governance cycle might also mean less flexibility in terms of when AIPs get called to vote.
Thanks to @astholder for the suggestion of what to do if no AIPs are ready
Copyright and related rights waived via CC0.
Notes: This AIP was formerly proposed under AIP 21