0. Proposer Info
- Email:
[insert proposer email] - Proposer’s Project Name:
[insert project name] - Proposer’s X (Twitter) Account:
[insert X profile URL] - Affiliation:
[State whether proposer is affiliated with the protocol or a token in the pool]
1. TL;DR
A concise summary of the proposal (3–5 bullet points). Ideally answer who, what, and why in a short, easy-to-skim format.
- Key Point #1
- Key Point #2
- Key Point #3
2. Background
Provide context for why this proposal exists:
- Problem/Opportunity: Outline the issue or opportunity this proposal aims to address.
- Relevant History: Reference any previous proposals, community calls, or forum threads that led to this.
- Stakeholder Impact: Who benefits or is affected (token holders, validators, developers, etc.)?
3. Proposal Details
Explain the core changes or actions you’re proposing. Include technical or financial specifics here—numbers, links to code, and references to any docs.
4. Rationale & Impact
- Motivation: Why is this proposal the best approach?
- Benefits: Summarize potential positive outcomes (e.g., security improvement, user adoption, ecosystem growth).
- Risks: Identify any known risks, drawbacks, or challenges. If possible, include how you’ll mitigate them.
Governance Votes
Yes
– You agree with implementing this proposal as outlined.
No
– You disagree with the proposal and do not support implementing it.
No with Veto
– You believe this proposal is spam, not relevant, incomplete, or harmful.
Abstain
– You do not have a strong opinion either way, but want to count toward quorum.
References / Appendix
(Optional)
- Provide links to code repositories, documentation, or forum discussions.
- Any data or graphs supporting your proposal.
- Additional clarifications or notes as needed.