Proposals

Learn how to create, submit, and manage governance proposals that can shape the future of DI Network.

Proposal Overview

What are Governance Proposals?

Governance proposals are formal suggestions for changes to DI Network that the community votes on. Successful proposals become binding protocol changes.

Types of Proposals

Parameter Changes:

• Trading fee adjustments

• Collateral ratio modifications

• Staking reward updates

• Liquidation threshold changes

Protocol Upgrades:

• New feature implementations

• Smart contract upgrades

• Security improvements

• Performance optimizations

Treasury Management:

• Development funding

• Marketing budgets

• Partnership investments

• Emergency fund allocations

Asset Management:

• New synthetic asset listings

• Collateral asset additions

• Asset parameter updates

• Asset deprecation decisions

Proposal Requirements

Minimum Requirements

Voting Power: 100,000 DI voting power required Technical Specification: Clear implementation details Community Support: Evidence of community interest Impact Analysis: Expected effects on protocol

Proposal Thresholds

Proposal Creation Requirements:
┌─────────────────────────────────────┐
│ Minimum Voting Power: 100,000 DI   │
│ Proposal Bond: 10,000 DI           │
│ Review Period: 3 days              │
│ Voting Period: 7 days              │
│ Quorum Required: 10% of supply     │
│ Approval Threshold: 50%+           │
│ Execution Delay: 48 hours          │
└─────────────────────────────────────┘

Proposal Bond

Bond Mechanism:

• 10,000 DI bond required for proposal submission

• Bond returned if proposal reaches quorum

• Bond forfeited if proposal fails to reach quorum

• Prevents spam and ensures serious proposals

Pre-Proposal Process

Step 1: Community Discussion

Forum Discussion:

• Post initial idea in governance forum

• Gather community feedback and input

• Refine proposal based on suggestions

• Build consensus and support

Discussion Template:

# [Pre-Proposal] Title

## Problem Statement
What issue does this proposal address?

## Proposed Solution
High-level approach to solving the problem.

## Expected Benefits
How will this improve the protocol?

## Potential Risks
What could go wrong?

## Community Input Needed
Specific feedback you're seeking.

Step 2: Technical Feasibility

Technical Review:

• Assess implementation complexity

• Identify required resources

• Estimate development timeline

• Consider security implications

Developer Consultation:

• Engage with core developers

• Review technical specifications

• Validate implementation approach

• Estimate gas costs and performance impact

Step 3: Stakeholder Analysis

Impact Assessment:

• Identify affected stakeholders

• Analyze benefits and costs for each group

• Consider unintended consequences

• Plan communication strategy

Proposal Creation

Proposal Structure

# Proposal Title: [Clear, Descriptive Title]

## Summary
Brief 2-3 sentence overview of the proposal.

## Motivation
### Problem Statement
Detailed description of the issue being addressed.

### Why Now?
Urgency and timing considerations.

## Specification
### Technical Details
Precise implementation specifications.

### Parameters
Specific values and configurations.

### Smart Contract Changes
Required contract modifications.

## Implementation
### Timeline
Phased implementation plan with milestones.

### Resources Required
Development, audit, and deployment resources.

### Dependencies
Prerequisites and coordination requirements.

## Analysis
### Benefits
Expected positive outcomes.

### Risks and Mitigation
Potential negative consequences and how to address them.

### Alternatives Considered
Other approaches that were evaluated.

## Success Metrics
How to measure if the proposal achieves its goals.

## Conclusion
Summary and call to action.

Writing Best Practices

Clarity and Precision:

• Use clear, non-technical language where possible

• Define technical terms and acronyms

• Provide specific numbers and parameters

• Include visual aids when helpful

Comprehensive Coverage:

• Address potential objections

• Consider edge cases and failure modes

• Provide implementation details

• Include rollback procedures if needed

Proposal Submission

Submission Process

1. Finalize Proposal: Complete all sections thoroughly

2. Prepare Bond: Ensure 10,000 DI available for bond

3. Submit On-Chain: Use governance interface to submit

4. Confirm Transaction: Verify proposal appears in system

5. Begin Advocacy: Start promoting proposal to community

Submission Interface

Proposal Submission Form:
┌─────────────────────────────────────┐
│ Title: Reduce DSwap Trading Fees    │
│ Category: Parameter Change          │
│ Bond Amount: 10,000 DI             │
│ Implementation: Immediate           │
│                                     │
│ Proposal Text: [Rich Text Editor]   │
│                                     │
│ Target Contracts: [Contract List]   │
│ Function Calls: [Call Data]        │
│                                     │
│ [Submit Proposal] [Save Draft]      │
└─────────────────────────────────────┘

Technical Implementation

Smart Contract Calls:

// Example proposal submission
const proposalData = {
  title: "Reduce DSwap Trading Fees",
  description: proposalMarkdown,
  targets: [DSWAP_CONTRACT_ADDRESS],
  values: [0],
  calldatas: [
    dswap.interface.encodeFunctionData("setTradingFee", [25]) // 0.25%
  ]
}

await governor.propose(
  proposalData.targets,
  proposalData.values,
  proposalData.calldatas,
  proposalData.description
)

Proposal Advocacy

Building Support

Community Engagement:

• Present proposal in community calls

• Answer questions in discussion forums

• Create educational content

• Address concerns and objections

Stakeholder Outreach:

• Engage with large token holders

• Reach out to delegates

• Connect with affected user groups

• Build coalitions of support

Communication Strategy

Multi-Channel Approach:

• Discord: Real-time discussion and Q&A

• Forum: Detailed technical discussions

• Twitter: Broad community awareness

• Medium: Long-form explanatory content

Content Creation:

Advocacy Content Plan:
Week 1: Proposal announcement and overview
Week 2: Technical deep-dive and FAQ
Week 3: Stakeholder impact analysis
Week 4: Final push and voting reminders

Addressing Opposition

Constructive Engagement:

• Listen to concerns respectfully

• Provide data-driven responses

• Consider proposal modifications

• Find compromise solutions when possible

Common Objections:

• Technical complexity or risk

• Economic impact concerns

• Implementation timeline issues

• Precedent and governance concerns

Proposal Management

During Voting Period

Active Monitoring:

• Track voting progress and participation

• Monitor community sentiment

• Address last-minute concerns

• Coordinate with supporters

Voting Dashboard:

Proposal #47 Status:
┌─────────────────────────────────────┐
│ Time Remaining: 2 days, 14 hours   │
│ Participation: 14.2% (Quorum Met)  │
│ Current Results:                    │
│   For: 72.1% (1,847,293 votes)    │
│   Against: 24.3% (622,847 votes)   │
│   Abstain: 3.6% (92,156 votes)     │
│ Trend: Steady support              │
│ Delegate Votes: 8/12 major delegates│
└─────────────────────────────────────┘

Post-Vote Activities

If Proposal Passes:

• Coordinate implementation with developers

• Monitor execution during timelock period

• Communicate timeline to community

• Track success metrics post-implementation

If Proposal Fails:

• Analyze voting patterns and feedback

• Identify reasons for failure

• Consider revised proposal if appropriate

• Thank community for participation

Proposal Types Deep Dive

Parameter Change Proposals

Common Parameters:

Trading Fees:
Current: 0.30%
Proposed: 0.25%
Impact: Increased trading volume, reduced revenue
Justification: Competitive positioning

Collateral Ratios:
Current: ETH 150%
Proposed: ETH 140%
Impact: Increased capital efficiency, higher risk
Justification: Market maturity, risk assessment

Treasury Proposals

Funding Requests:

Development Grant Proposal:
Amount: 500,000 DI ($2.5M)
Purpose: Cross-chain expansion
Timeline: 6 months
Milestones: 4 deliverable phases
Team: Established development team
Success Metrics: User adoption, TVL growth

Emergency Proposals

Fast-Track Process:

• Reduced discussion period (24 hours)

• Expedited voting (3 days)

• Higher quorum requirement (15%)

• Guardian pre-approval required

Proposal Analytics

Success Factors

Historical Analysis:

Proposal Success Rates by Type:
Parameter Changes: 78% success rate
Treasury Spending: 65% success rate
Protocol Upgrades: 82% success rate
Emergency Actions: 95% success rate

Success Factors:
- Clear problem statement: +25% success
- Community pre-discussion: +30% success
- Developer support: +40% success
- Stakeholder engagement: +20% success

Performance Tracking

Proposal Metrics:

• Community engagement levels

• Voting participation rates

• Implementation success rates

• Post-implementation outcomes

Best Practices

Proposal Creation

• Start with community discussion

• Gather technical feasibility input

• Build stakeholder support

• Write clear, comprehensive proposals

• Include implementation details

Community Engagement

• Engage early and often

• Listen to feedback and concerns

• Provide regular updates

• Be responsive to questions

• Build coalitions of support

Technical Excellence

• Provide precise specifications

• Consider security implications

• Plan for edge cases

• Include rollback procedures

• Coordinate with developers

Post-Submission

• Monitor voting progress

• Address concerns promptly

• Coordinate implementation

• Track success metrics

• Learn from outcomes

Common Pitfalls

Proposal Failures

Insufficient Preparation:

• Lack of community discussion

• Poor technical specification

• Inadequate stakeholder analysis

• Rushed submission process

Communication Issues:

• Unclear problem statement

• Technical jargon overuse

• Inadequate advocacy

• Poor timing of submission

Technical Problems:

• Implementation complexity underestimated

• Security risks not addressed

• Gas costs too high

• Incompatible with existing systems

Avoiding Mistakes

• Start with thorough preparation

• Engage community early and often

• Get technical review before submission

• Plan comprehensive advocacy strategy

• Learn from previous proposals

Future Improvements

Governance Evolution

Planned Enhancements:

• Improved proposal templates

• Better technical review processes

• Enhanced community engagement tools

• Streamlined implementation workflows

Staying Engaged

• Participate in governance improvement discussions

• Provide feedback on proposal processes

• Help mentor new proposal creators

• Contribute to governance tooling development