E. Proposal Classification and Standards

1)Proposal Types: To improve governance efficiency, we classify proposals into three levels, each with different processing flows and requirements:

Lightweight proposals (prioritize off-chain processing) - These proposals mainly involve noncritical community affairs and daily operations:

Community initiatives: Including community activity organization, promotional plans, community rule-making, etc. These proposals typically only need off-chain consensus, executable after reaching agreement through forum discussion.

Ecosystem cooperation: Preliminary cooperation intentions, resource connections, joint marketing, etc. These typically serve as exploratory discussions, not requiring immediate on-chain commitment.

Improvement suggestions: User interface optimization, documentation improvement, tool enhancement, etc. These can be handled through GitHub Issues or improvement proposals.

Standard proposals (off-chain discussion + on-chain decision) - Proposals involving network operations but not touching core architecture:

Parameter adjustments: Regular adjustments to fee rates, staking reward rates, validator counts, and other parameters. These adjustments require data analysis and simulation testing.

Medium fund allocation: Community grants under $100,000, developer rewards, marketing budgets, etc. Require clear budget plans and performance indicators.

Feature updates: Adding non-critical features, optimizing existing features, integrating thirdparty services, etc. Require detailed technical solutions and test results.

Major proposals (mandatory on-chain governance) - Critical decisions with profound network impact:

Protocol upgrades: Consensus mechanism modifications, core smart contract updates, network forks, etc. Must undergo complete technical evaluation and security audit.

Economic model adjustments: Fundamental economic parameter modifications to token supply mechanisms, inflation models, burn mechanisms, etc. Require detailed economic analysis and simulation.

Large fund utilization: Fund allocations exceeding $100,000, strategic investments, acquisitions, etc. Require professional financial evaluation and risk analysis.

Emergency response measures: Security incident handling, network recovery, emergency forks, etc. Despite time constraints, must still follow minimum necessary principles.

2)Proposal Standards: All on-chain proposals must follow standardized format requirements:

Basic information:

– Proposal title: Concise and clear, not exceeding 100 characters

Proposal type: Clearly marked category

Urgency level: Regular/Urgent/Critical

Proposer information: Including on-chain address and off-chain contact information

Impact assessment:

Impact scope: Affected modules, user groups, ecosystem projects

Expected results: Quantitative and qualitative success indicators

Time planning: Detailed implementation timeline and key milestones

Background explanation:

Problem statement: Clear description of the problem to be solved

Current state analysis: Current handling methods and their shortcomings

Necessity justification: Why this change is needed now

Solution design:

Technical solution: Detailed technical architecture and implementation path

Implementation steps: Phased execution plan

Resource requirements: Human resources, funding, time, and other resource assessments

Risk management:

Risk identification: Technical risks, economic risks, execution risks, etc.

Impact analysis: Potential losses in worst-case scenarios

Mitigation measures: Response plans for each risk

Rollback plan: Recovery plan in case of failure

Smart contract calls:

Target contract addresses and function signatures

Precise parameter values and data types

Gas limits and estimated costs

Multi-sig wallet addresses and required signature counts

Step-by-step transaction sequences

Verification checkpoints for each step

Contingency plans:

Rollback trigger conditions

Rollback execution steps

Data backup and recovery solutions