The Obol Collective encourages proposers to include the following sections for proposals:
Proposal Title: What is the name of your proposal?
Status: [Draft] / [Final]
Proposal Type:[Type] Governance proposals must correspond to a valid proposal type as described in the official documentation.
Abstract: Two or three sentences that summarize the proposal.
Motivation: Explain why the Obol Collective should implement this proposal. Please disclose any actual or anticipated conflicts of interest that you (as an individual, group, or entity) may have concerning this proposal.
Specifications: Detail the specifics of the proposal. Please include: Technical details (a comprehensive description of the proposed changes).
If applicable, please include:
- Links to all APIs/ tech specifications
- Overview of ongoing security considerations, including all audits and findings
- Impact summary (a comprehensive description of the consequences of adopting the proposed changes).If applicable, please include:
- Changes in performance characteristics
- Time-of-upgrade considerations (downtime, etc.)
- Links to exhaustive upgrade documentation for impacted stakeholders
Action Plan: Outline how the proposal would be implemented. If applicable, please include:
- Expected timing for implementation/upgrade/execution.
- Contingency plans to address potential last-minute bugs or issues.
- Plans for communication and education for the community.
Conclusion: Wrap up your proposal.
Please include:
- Recap of main points
- Request for approval
Note: By submitting a proposal, you represent and warrant to the Obol Collective that all the information provided is accurate and complete to the best of your knowledge.