Title: [SIP#] TITLE
Authors: Date:
tl;dr
- Provide a brief 2-3 sentence summary of the proposal, outlining its objectives and intended outcomes.
- Add the prefix [Tempchack] or [RFC] or [SIP].
- Once the proposal passes Snapshot, it will be assigned an SIP number.
MOTIVATION
In this section, the primary goal is to delve into the author’s motivation behind the SIP, focusing on the “why” aspect. To address this, the author should explore several key questions:
- Are there any loopholes or shortcomings in the current established processes within the DAO that demand attention?
- Is there a need for improvements or adjustments in the existing procedures to enhance efficiency, transparency, or security?
- Are there identified opportunities that could significantly improve the overall state of the DAO?
- Can the proposed SIP capitalize on potential advantages, such as new technologies, partnerships, or strategic initiatives?
- Are there prevalent challenges or issues faced by a substantial number of DAO members that necessitate changes or focused attention?
- Does the SIP aim to resolve specific problems experienced by the community, thereby fostering a more inclusive and supportive environment?
By thoroughly addressing these questions, the author can articulate a compelling narrative about the motivation behind the SIP. This will provide clarity on whether the proposal aims to rectify existing deficiencies, seize opportunities for improvement, or address challenges faced by the DAO community.
SPECIFICATION
The specification should detail the scope and the proposal. Technical proposals should include detailed documentation that enables an external development team to implement if needed.
Questions to consider:
- Does the proposal require new code?
- How is the security of the code ensured?
- Who is responsible for its implementation?
- What is the expected timeline?
- What are the anticipated financial implications of the proposal?
- If requesting a budget, provide a detailed breakdown of how the funds will be used and outline key milestones to measure the success of the initiative.
Rationale
This part is about backing up why you’re going with this solution and how you decided on it. Think of it like explaining why you picked a certain way when there were other options. We want to know why you like this one and why you said no to the others. Also, if there’s something special about your team or what pushes you to suggest this, you can put that in here too.
NEXT STEPS
- Immediate action items, should this proposal be accepted
CONCLUSION
- 2-3 sentence conclusion on the proposal and its importance to the community
Copyright
Copyright and related rights waived via CC0 1.0 license.