Guidelines on new Proposals
Proposals for common operations already supported by the governance app (such as adding Points of Interest, adding a Catalyst, or banning a name), don’t require a forum post, and can be dealt with completely on-chain. These proposals may include a forum post anyway, allowing the author to explain their motivations.
Proposals that require on-chain changes (such as changing the DAO configuration, issuing funds for projects, etc) should be reviewed by the SAB or technical community members, and include the proposed changes execution in the DAO vote (ie: don’t issue a “Question” vote if you want actual on-chain changes to be made). If you don’t know how to get your proposal to be executed on chain, or you’re unsure if it’s even possible, feel free to ask in your forum post.
When creating a new post make sure you:
- Stick to the template below.
- Write concise title with no number. The number will be added by mods once on-chain voting starts.
- Add understandable, non-tech, ELI-5 summary.
- Add an abstract: what will be done if the DIP is implemented (keep it below 200 words).
- Write a longer motivation with links and references if necessary.
- Add specifications if necessary. You can also ask for help from technical community members to write necessary code or specifications.
- Formulate clear for and against positions. (i.e: what does it mean to vote Yes or No)
- You may include a poll to measure sentiment before sending on-chain if you want.
- Don’t rush with putting a proposal on chain, keep discussion going for at least 3 days.
- Submit the proposal on chain for voting using the governance app.
Status: DRAFT | ACCEPTED | REJECTED | WITHDRAWN
Simply describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.
A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what will be done if the DIP is implemented.
This is the problem statement. This is the why of the DIP. It should clearly explain why the current state of the protocol is inadequate.
This is a high level overview of how the DIP will solve the problem. The overview should clearly describe how the new feature will be implemented.