Skip to main content

GnosisDAO GIP Template

How to use this template
  • Keep each section concise and link out to deeper docs where needed.
  • Only include the sections marked as required for your proposal type.
  • Follow the How to create a GIP guide for step-by-step guidance.

Header (required)

GIP: [number]
title: [Full title]
author: [Name(s), GitHub username(s), email]
status (reflected by tag): [Draft | Review | Voting | Approved | Rejected]
created: [YYYY-MM-DD]

1. Abstract (required)

Brief overview. Two to three sentences maximum.

Abstract:
[One-paragraph summary of what this proposal does and why it matters]

2. Motivation and problem statement (required)

Motivation:
- Problem 1: [What issue does this address?]
- Problem 2: [Secondary issue]
- Why now: [Why is this urgent or important?]

3. Specification (required for Technical and Product)

Specification:
- Proposed change: [Detailed description]
- Technical implementation: [Smart contract changes, if any]
- Parameters: [Exact values, addresses, thresholds]

4. Budget and funding (required if funding is involved)

Budget:
- Total requested: [Amount in GNO or USD]
- Breakdown:
- Item 1: [Amount]
- Item 2: [Amount]
- Payment schedule: [Milestone-based | Upfront | Monthly]

5. Timeline and milestones (required for projects over 50k)

Timeline:
- Phase 1: [Description]
- Duration: [X weeks]
- Deliverable: [What completes phase]
- Funding: [Amount]

- Phase 2: [If applicable]
- Duration: [X weeks]
- Deliverable: [What completes phase]
- Funding: [Amount]

Success metrics:
- Metric 1: [How to measure success]
- Metric 2: [Secondary metric]
Risks:
- Risk 1: [Description]
- Likelihood: [Low | Medium | High]
- Mitigation: [How to reduce risk]

- Risk 2: [Description]
- Likelihood: [Low | Medium | High]
- Mitigation: [How to reduce risk]
Alternatives:
- Option A: [Description]
- Why not chosen: [Reason]
- Option B: [Description]
- Why not chosen: [Reason]

8. Conclusion

Conclusion:
[Summarize why this should pass and what success looks like]