📋Proposal Guidelines
Learn how to create effective proposals that benefit the 0QP community.
Types of Proposals
Protocol Upgrades
Technical improvements:
Smart contract updates: Bug fixes and optimizations
New features: Trading tools and functionality
Security enhancements: Additional protection measures
Performance improvements: Speed and efficiency gains
Economic Changes
Tokenomics modifications:
Fee adjustments: Trading spread changes
Rewards distribution: Staking and LP reward rates
Burn rate changes: Token deflationary adjustments
Treasury allocation: Spending priorities
Governance Changes
DAO improvements:
Voting thresholds: Quorum and approval requirements
Proposal process: Timeline and requirement changes
Committee structure: New committees or role changes
Emergency procedures: Crisis response updates
Strategic Initiatives
Growth and partnerships:
Chain integrations: New blockchain additions
Partnership proposals: Strategic collaborations
Marketing campaigns: Community growth initiatives
Grant programs: Developer incentive programs
Proposal Requirements
Minimum Requirements
What every proposal needs:
10,000 0QP bond: Required to submit proposal
Clear title: Maximum 60 characters
Detailed description: Minimum 500 words
Implementation timeline: Realistic deadlines
Impact assessment: Expected outcomes
Proposal Structure
Required Sections:
Executive Summary (100 words max)
Problem Statement (200 words max)
Proposed Solution (500+ words)
Implementation Plan (300+ words)
Risk Analysis (200+ words)
Success Metrics (100+ words)
Technical Proposals
Additional requirements for technical changes:
Code specifications: Detailed technical implementation
Security review: Audit requirements and timeline
Testing plan: Comprehensive testing approach
Rollback plan: Emergency reversal procedure
Pre-Submission Process
Community Discussion Phase
Before formal submission (7+ days):
Discord Discussion:
#governance-ideas: Initial concept sharing
#governance-discussion: Detailed debate
Community calls: Live discussion sessions
Feedback collection: Gather suggestions
Forum Discussion:
Temperature check: Gauge initial support
Detailed feedback: Technical and economic review
Iteration process: Refine based on input
Coalition building: Find supporters
Stakeholder Engagement
Key groups to consult:
Technical Committee:
Security implications: Review safety concerns
Implementation feasibility: Technical possibility
Resource requirements: Development needs
Timeline assessment: Realistic scheduling
Economic Committee:
Financial impact: Treasury and tokenomics effects
Cost-benefit analysis: Value proposition review
Market implications: Trading and liquidity effects
Risk assessment: Potential negative outcomes
Proposal Refinement
Iterate based on feedback:
Address concerns: Respond to all major objections
Incorporate suggestions: Improve based on input
Clarify details: Remove ambiguity
Update timeline: Realistic implementation schedule
Final review: Internal quality check
Submission Process
Formal Submission
Steps to submit proposal:
Finalize proposal text in required format
Visit vote.0qp.finance/submit
Connect wallet with 10K+ 0QP
Fill proposal form with all details
Submit and pay bond (10K 0QP locked until vote)
Post-Submission Review
Technical review period (24 hours):
Format verification: Check all required sections
Technical feasibility: Security committee review
Legal compliance: Regulatory considerations
Publication: Add to official voting platform
Campaign Period
Build support during voting (5 days):
Social media: Twitter, Discord promotion
Community outreach: Direct voter engagement
Address concerns: Respond to new questions
Monitor progress: Track voting trends
Writing Effective Proposals
Best Practices
Clear Communication:
Simple language: Avoid unnecessary jargon
Logical structure: Easy to follow format
Visual aids: Charts and diagrams when helpful
Concise writing: Respect reader's time
Strong Arguments:
Data-driven: Use metrics and evidence
Problem focus: Clearly define issues addressed
Solution benefits: Highlight positive outcomes
Risk mitigation: Address potential concerns
Common Mistakes to Avoid
Content Issues:
❌ Vague objectives: Unclear goals and outcomes
❌ Missing details: Insufficient implementation info
❌ Unrealistic timeline: Overly ambitious scheduling
❌ Ignored risks: Failure to address concerns
Process Issues:
❌ No pre-discussion: Skipping community feedback
❌ Last-minute submission: Rushed proposal creation
❌ Poor engagement: No campaign during voting
❌ Inadequate research: Insufficient background work
Proposal Examples
Successful Proposal Template
Proposal Checklist
Before submission verify:
✅ All sections complete: No missing required parts
✅ Word count met: Minimum requirements satisfied
✅ Community discussed: Pre-submission feedback gathered
✅ Technical review: Security implications considered
✅ Timeline realistic: Achievable implementation schedule
✅ Bond available: 10K 0QP ready to lock
✅ Support building: Campaign strategy ready
After Submission
During Voting Period
Active campaign (5 days):
Daily updates: Share voting progress
Address questions: Respond to new concerns
Engage voters: Direct outreach to large holders
Media push: Social media promotion
If Proposal Passes
Implementation phase:
Bond returned: 10K 0QP unlocked
Execution oversight: Monitor implementation
Progress updates: Regular community reports
Success measurement: Track defined metrics
If Proposal Fails
Learning and iteration:
Bond forfeited: 10K 0QP sent to treasury
Failure analysis: Understand rejection reasons
Community feedback: Gather improvement suggestions
Potential resubmission: Address concerns and retry
Getting Support
Building Coalitions
Key supporter groups:
Large token holders: Significant voting power
Committee members: Technical expertise and influence
Community leaders: Trusted voices and networks
Delegates: Represent many smaller holders
Communication Channels
Reach voters through:
Discord campaigns: Targeted channel outreach
Twitter threads: Public proposal explanations
Community calls: Live Q&A sessions
Direct messages: Personal voter engagement
Success tip: Spend 2 weeks in community discussion before submitting. Well-prepared proposals have 3x higher success rate.
Last updated