As we enter V3 governance, the proposal flow must necessarily change as we move from the launch team developing and deploying off-chain approved proposals to fully on-chain proposal execution.
Because the ultimate execution is now on-chain, I believe we should implement a more effective proposal filtration process, taking significant inspiration from YFI’s example. This will allow for deeper discussion of ideas, stronger proposals, less clutter, and in general a more diligent and streamlined flow.
The high level process will be:
Forum Discussion + Poll > Off-chain Signalling > Code Production > On-chain Vote
To standardize the first step, we will utilize an informal process similar to YFI’s:
- Stick to the auto-generated template.
- Write a concise title with no number. The number will be added by mods once off-chain vote signing starts.
- Add understandable (aka non-tech/eli-5) summary.
- Add an abstract: what will be done if the YIP is implemented (keep it below 200 words).
- Write a longer motivation with links and references if necessary.
- Add specifications if necessary.
- Formulate clear for and against positions for binary proposals, or a scale of options with an “Against” option for numerically based proposal (eg. rewards should be “1%”, “2%”, “3%”, or “Against Proposal”)
- Include a poll to measure sentiment (public, results on vote).
- Don’t rush submitting a snapshot proposal, keep discussion going for at least 3 days.
Once the forum discussion has concluded, a proposal can be made using the same structure through the Snapshot portal. The results of this token-weighted vote will serve as signal for code development, the deployment and execution of which will require a fully on-chain ratification.
Please note that if the community approves of this new proposal flow, topics in the forum and proposals on Snapshot will begin to be filtered according to this process.