Proposal Lifecycle

Overview

Understanding the complete lifecycle of a governance proposal helps participants engage effectively with the Noderr Protocol's decision-making process.

Proposal Stages

Stage 1: Ideation (Informal)

Duration: Ongoing

Activities:

  • Community discusses ideas on Discord/Forum
  • Informal temperature checks
  • Concept refinement
  • Coalition building

No formal requirements

Stage 2: Draft Proposal

Duration: 1-2 weeks

Requirements:

  • Detailed proposal document
  • Implementation specification
  • Cost/benefit analysis
  • Risk assessment

Template:

# Proposal Title## Summary
Brief description (2-3 sentences)
## Motivation
Why is this needed?
## Specification
Technical details and implementation
## Rationale
Why this approach?
## Security Considerations
Potential risks and mitigations
## Economic Impact
Effect on tokenomics and treasury
## Implementation Timeline
Phases and milestones

Stage 3: Temperature Check

Duration: 3-5 days

Method: Off-chain poll (Snapshot)

Purpose:

  • Gauge community interest
  • Identify concerns early
  • Refine proposal before formal submission

Threshold: >60% support to proceed

Stage 4: Formal Submission

Requirements:

  • 100,000 NODR stake OR
  • Guardian/Oracle node status OR
  • Protocol team submission

Submission Fee: 1,000 NODR (refunded if proposal passes)

On-Chain Actions:

// Submit proposal
governanceManager.submitProposal(
proposalData,
executionCalldata,
description
);

Stage 5: Discussion Period

Duration: 7 days

Activities:

  • Forum discussion thread created
  • Community asks questions
  • Proposer provides clarifications
  • Revisions possible (creates new version)

Key Participants:

  • Proposal author
  • Community members
  • Technical reviewers
  • Protocol team (advisory)

Stage 6: Voting Period

Duration: 7 days

Voting Opens: Automatically after discussion period

Both Chambers Vote:

  • Token holders vote with staked NODR
  • Node operators vote with TrustFingerprint™-weighted power

Real-Time Results: Visible throughout voting period

Stage 7: Timelock

Duration: 48 hours (standard) or 24 hours (emergency)

Purpose:

  • Allow community to prepare for changes
  • Enable emergency response if needed
  • Provide transparency before execution

Can Be Cancelled: By protocol multisig if critical issue discovered

Stage 8: Execution

Trigger: Automatic after timelock expires

Process:

  • Smart contracts execute approved changes
  • On-chain parameters updated
  • Treasury allocations distributed
  • Protocol upgrades applied

Verification: All actions are onchain and verifiable

Stage 9: Post-Implementation

Duration: Ongoing

Activities:

  • Monitor implementation effects
  • Collect community feedback
  • Assess success metrics
  • Document lessons learned

Proposal Outcomes

Passed

Requirements Met:

  • Quorum achieved in both chambers
  • Majority/supermajority vote in favor
  • No critical issues during timelock

Next Steps:

  • Timelock period begins
  • Execution scheduled
  • Community notified

Rejected

Reasons:

  • Failed to achieve quorum
  • Majority voted against
  • Withdrawn by proposer

Next Steps:

  • Proposal archived
  • Submission fee forfeited (if applicable)
  • Can be resubmitted with modifications after 30 days

Cancelled

Reasons:

  • Critical security issue discovered
  • Proposer withdraws
  • Superseded by emergency proposal

Next Steps:

  • Submission fee refunded
  • Explanation provided to community

Special Proposal Types

Parameter Change Proposals

Examples:

  • Fee adjustments
  • Reward rates
  • Risk limits

Fast Track: Can skip temperature check if minor

Treasury Proposals

Examples:

  • Grant allocations
  • Protocol expenses
  • Strategic investments

Additional Requirements:

  • Detailed budget
  • Milestone-based distribution
  • Accountability measures

Technical Upgrade Proposals

Examples:

  • Smart contract upgrades
  • Protocol improvements
  • New feature additions

Additional Requirements:

  • Audit reports
  • Testing results
  • Rollback plan

Emergency Proposals

Examples:

  • Security patches
  • Critical bug fixes
  • Immediate protocol actions

Expedited Process:

  • 24-hour voting period
  • Lower quorum acceptable
  • Guardian/Oracle approval required

Proposal Metrics

Track proposal performance:

MetricTargetCurrent
Participation Rate>20%TBD
Average Voting PowerBalancedTBD
Proposal Success Rate60-70%TBD
Time to Execution<14 daysTBD

Best Practices

For Proposers

  1. Start with Discussion: Gauge interest before formal submission
  2. Be Detailed: Provide comprehensive specifications
  3. Engage Actively: Respond to questions promptly
  4. Be Flexible: Willing to revise based on feedback
  5. Plan Implementation: Have clear execution plan

For Voters

  1. Read Thoroughly: Understand full implications
  2. Ask Questions: Seek clarification if needed
  3. Vote Consistently: Build participation bonus
  4. Consider Long-Term: Think beyond immediate impact
  5. Delegate Wisely: If delegating, choose carefully

Tools and Resources

Proposal Tools

Templates

  • Proposal template (above)
  • Budget template
  • Technical specification template

Analytics

  • Governance dashboard
  • Voting history
  • Proposal archive

See Also:

results matching ""

    No results matching ""