1. TL;DR
This proposal recommends modifying [insert contract name] to [briefly explain the purpose or motivation behind the change].
The update aims to:
- [Goal 1] – [Concise explanation of how this goal is achieved or addressed]
- [Goal 2] – [Explanation]
- [Goal 3] – [Explanation]
2. Background
Current State
- Provide a brief summary of the existing contract/module and its function.
Motivation for Change
- Outline the specific issues or limitations with the current setup.
- Explain what’s driving the update. e.g., product evolution, technical improvements, community input, sybil resistance, UX enhancements, etc.
- Include any relevant data, feedback, or observations from the community that support this proposal.
3. Proposed Changes
Updated Modules
- List the specific modules, contracts, or components that will be modified.
Related Pull Requests
- Link to the PR(s) that contain the implementation details or relevant code changes.
4. Technical Implementation Plan
- Provide a timeline or conditions for deployment.
- Include any coordination needs (e.g., validator upgrade, migration steps, etc.).
Governance Vote Options
- YES – You support implementing the proposed update.
- NO – You do not support the proposed change.
- NO WITH VETO – You believe the proposal is harmful, spam, or violates governance principles.
- ABSTAIN – You choose not to take a position but want your vote counted toward quorum.