Please include a clear, concise title beginning with [Proposal]. Keep in mind that your proposal will be much better received and will lead to far more productive discussions if it is focused, includes sufficient background information, and has action points that are easy to understand. Furthermore, please structure your proposal as modeled below, and for more information on the CIP process, see our docs.
Summary
“If you can’t explain it simply, you don’t understand it well enough.” Simply describe the outcome the proposed change intends to achieve. This should be non-technical and accessible to a casual community member.
Background
This section should include any relevant information that the community needs to know before reading the rest of your proposal, such as a short introduction to any concepts that will be discussed. Additionally, this section is an ideal place to clarify points that are within the scope of your proposal and those that are relevant but remain outside the scope of the present proposal.
Motivation
This is the problem statement. This is the why of the CIP. It should clearly explain why the current state of the protocol is inadequate. It is critical that you explain why the change is needed. For instance, if the CIP proposes changing how something is calculated, you must address why the current calculation is inaccurate or wrong. This section may also include why certain design choices were made over others, and can include data from previous discussions and forum posts.
Specification
This section details how the CIP will solve the problem, and should clearly and succinctly describe how the new feature will be implemented.
Additionally, you should include clearly defined, unbiased For and Against options along with a poll to gauge sentiment.
For:
Against:
Poll:
If you have any additional questions, feel free to reach out to the team on Discord.
