|
| 1 | +--- |
| 2 | +title: Governance Participation |
| 3 | +description: Understanding voting rights, power delegation, and governance mechanisms for TORUS token holders. |
| 4 | +--- |
| 5 | + |
| 6 | +import { |
| 7 | + Aside, |
| 8 | + Card, |
| 9 | + CardGrid, |
| 10 | + Code, |
| 11 | + Tabs, |
| 12 | + TabItem, |
| 13 | +} from "@astrojs/starlight/components"; |
| 14 | + |
| 15 | +Governance participation enables TORUS token holders to shape the network's evolution through democratic decision-making processes. Every token holder has voting rights proportional to their holdings, creating a decentralized governance system where community consensus drives protocol changes. |
| 16 | + |
| 17 | +The Torus DAO operates on principles of transparency, inclusivity, and token-weighted voting, ensuring that those with the most stake in the network's success have proportional influence over its direction. |
| 18 | + |
| 19 | +## Voting Power and Token Weight |
| 20 | + |
| 21 | +### Voting Power Calculation |
| 22 | +Voting power directly correlates to TORUS token holdings: |
| 23 | +- **1 TORUS = 1 vote** |
| 24 | +- Voting power is calculated at proposal snapshot time |
| 25 | +- Staked tokens may have additional voting weight (depending on staking mechanics) |
| 26 | +- Tokens must be held in your connected wallet during voting periods |
| 27 | + |
| 28 | +### Power User vs Delegated Voting |
| 29 | + |
| 30 | +**Delegated Voting (Default)** |
| 31 | +- Validators automatically vote on behalf of token holders |
| 32 | +- No action required from individual holders |
| 33 | +- Validators make decisions based on their assessment of proposals |
| 34 | +- Reduces participation burden for passive holders |
| 35 | +- Can be changed to personal voting at any time |
| 36 | + |
| 37 | +**Power User Mode** |
| 38 | +- Direct control over your voting decisions |
| 39 | +- Must actively participate in each proposal vote |
| 40 | +- Full autonomy over how your tokens influence governance |
| 41 | +- Requires transaction to enable/disable |
| 42 | +- Ideal for active community members who want direct control |
| 43 | + |
| 44 | +## Proposal Types and Voting |
| 45 | + |
| 46 | +### Treasury Transfer Proposals |
| 47 | +Community requests for funding from the DAO Treasury to support ecosystem development, research, or community initiatives. |
| 48 | + |
| 49 | +**Voting Considerations:** |
| 50 | +- Project viability and team credibility |
| 51 | +- Benefit to the Torus ecosystem |
| 52 | +- Budget reasonableness and timeline |
| 53 | +- Alignment with network priorities |
| 54 | + |
| 55 | +### Emission Proposals |
| 56 | +Changes to network economics, including token emission rates, burn mechanisms, and reward distribution parameters. |
| 57 | + |
| 58 | +**Voting Considerations:** |
| 59 | +- Long-term economic sustainability |
| 60 | +- Impact on token value and inflation |
| 61 | +- Effects on network incentives |
| 62 | +- Technical feasibility of implementation |
| 63 | + |
| 64 | +### Governance Parameter Changes |
| 65 | +Modifications to voting thresholds, proposal costs, voting periods, and other governance mechanics. |
| 66 | + |
| 67 | +**Voting Considerations:** |
| 68 | +- Democratic accessibility vs governance security |
| 69 | +- Participation requirements and barriers |
| 70 | +- Protection against governance attacks |
| 71 | +- Community representation balance |
| 72 | + |
| 73 | +## Voting Mechanics |
| 74 | + |
| 75 | +### Proposal Lifecycle |
| 76 | +1. **Submission**: Proposals submitted with required deposit (typically 10,000 TORUS) |
| 77 | +2. **Review Period**: Community discussion and feedback (informal) |
| 78 | +3. **Voting Period**: 7-day voting window for all token holders |
| 79 | +4. **Execution/Rejection**: Automatic execution based on voting results |
| 80 | + |
| 81 | +### Approval Criteria |
| 82 | +**Standard Requirements:** |
| 83 | +- **Support Threshold**: At least 50% of votes must be favorable |
| 84 | +- **Participation Threshold**: More than 10% of total token supply must participate |
| 85 | +- **Time Limit**: Voting closes after 7 days regardless of participation |
| 86 | + |
| 87 | +**Outcome Scenarios:** |
| 88 | +- **Approved**: 50%+ support + 10%+ participation → Automatic execution |
| 89 | +- **Rejected**: Less than 50% support + 10%+ participation → Proposal fails |
| 90 | +- **Insufficient Participation**: Less than 10% participation → Proposal expires |
| 91 | + |
| 92 | +### Vote Finality |
| 93 | +Once cast, votes cannot be changed during the voting period. This ensures predictability and prevents last-minute manipulation, but requires careful consideration before voting. |
| 94 | + |
| 95 | +## Economic Incentives and Costs |
| 96 | + |
| 97 | +### Proposal Costs |
| 98 | +- **Submission Fee**: 10,000 TORUS required to submit proposals |
| 99 | +- **Cost Recovery**: Fee refunded if proposal passes, retained by Treasury if rejected |
| 100 | +- **Spam Prevention**: Economic barrier prevents frivolous proposals |
| 101 | + |
| 102 | +### Voting Costs |
| 103 | +- **Transaction Fees**: Standard network fees apply for voting transactions |
| 104 | +- **Power User Setup**: One-time transaction to enable direct voting control |
| 105 | +- **Switching Modes**: Small transaction cost to change between delegated and power user modes |
| 106 | + |
| 107 | +## Strategic Voting Considerations |
| 108 | + |
| 109 | +### Information Gathering |
| 110 | +- **Proposal Details**: Thoroughly review all proposal documentation |
| 111 | +- **Community Discussion**: Engage in Discord, Telegram, and forum discussions |
| 112 | +- **Technical Analysis**: Understand implementation details and potential impacts |
| 113 | +- **Precedent Setting**: Consider how current votes affect future proposals |
| 114 | + |
| 115 | +### Long-term Impact |
| 116 | +- **Network Health**: Vote for proposals that strengthen the ecosystem |
| 117 | +- **Economic Sustainability**: Support proposals that enhance long-term value |
| 118 | +- **Community Growth**: Favor initiatives that expand and engage the user base |
| 119 | +- **Innovation**: Encourage proposals that advance technical capabilities |
| 120 | + |
| 121 | +## Governance Security |
| 122 | + |
| 123 | +### Attack Prevention |
| 124 | +- **Proposal Costs**: Economic barriers prevent spam and low-quality submissions |
| 125 | +- **Time Delays**: Voting periods allow community review and response |
| 126 | +- **Participation Thresholds**: Ensure broad community involvement in decisions |
| 127 | +- **Transparent Process**: All votes and outcomes are publicly recorded |
| 128 | + |
| 129 | +### Best Practices |
| 130 | +- **Diversified Holdings**: Avoid concentration of voting power in few hands |
| 131 | +- **Active Participation**: Regular voting prevents governance capture |
| 132 | +- **Community Engagement**: Discuss proposals before voting |
| 133 | +- **Long-term Thinking**: Consider ecosystem health over short-term gains |
| 134 | + |
| 135 | +## Related Concepts |
| 136 | + |
| 137 | +- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - Understanding TORUS token economics and distribution |
| 138 | +- **[Staking](https://docs.torus.network/explanations/holders/staking/)** - How staking affects voting power and governance participation |
| 139 | +- **[Governance DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Overall DAO structure and decision-making processes |
| 140 | + |
| 141 | +<Aside type="tip" title="Ready to Start Voting?"> |
| 142 | + Follow our [step-by-step guide to vote on proposals](https://docs.torus.network/how-to-guides/holders/vote-on-proposals/) for practical instructions. |
| 143 | +</Aside> |
0 commit comments