The complete governance process consists of two main phases, each with clear time requirements and quality standards.1)Phase One: Off-chain Preparation Period: The off-chain preparation period is the critical phase for proposal maturation, typically lasting 2-4 weeks.
Discussion initiation (suggested 7-14 days)
Initial concept publication: Proposers create discussion topics in the governance forum, clearly stating the proposal’s background, objectives, and preliminary solutions. Posts must include problem statements, solution overviews, and expected impact analysis.
Community interaction deepening: Community members participate through replies, voting, and other methods. Proposers must actively respond, checking and replying to major questions at least daily. High-quality interaction often reveals potential problems and improvement opportunities.
Stakeholder coordination: Proactively contact potentially affected parties, including developers, validators, large token holders, ecosystem projects, etc., collecting their professional opinions and interests.
Proposal optimization (suggested 3-7 days)
Feedback integration and iteration: Systematically organize community feedback, identify common issues and constructive suggestions, and conduct multiple rounds of iterative optimization.Each major modification must be updated in the forum to maintain transparency.
Professional evaluation acquisition: Relevant committees conduct professional evaluations, producing comprehensive reports covering technical feasibility, economic impact, security risks,and other dimensions. These reports become important references for community decisions.
Signal voting validation: Conduct simulated voting through off-chain voting tools. If support rate is below 40%, continued optimization or proposal withdrawal is recommended. This mechanism helps proposers avoid unnecessary on-chain costs.
Final preparation
Document completion and finalization: Write complete technical specification documents,including implementation details, interface definitions, migration solutions, etc. Documents must be reviewed by professional technical writers to ensure accuracy and readability.
Code audit confirmation: If proposals involve smart contract changes, security audit reports from at least one reputable audit firm are required. Audit costs can be pre-paid from the community treasury upon application.
Timing selection strategy: Evaluate network status, market conditions, community sentiment, and other factors to choose appropriate on-chain submission timing. Avoid submitting important proposals during network congestion or extreme market volatility.
2)Phase Two: On-chain Decision Period: The on-chain decision period is the formal voting phase for proposals, with strict procedural requirements.
Formal submission (48-hour review period)
– Proposal on-chain process: Proposers submit complete proposals to governance contracts through the governance interface, including all necessary metadata, detailed content, and execution code. The system automatically verifies proposal format completeness.
Deposit lock mechanism: Pay corresponding deposits based on proposal type—different importance proposals require locking different deposit amounts, while also locking voting tokens required for the proposal.
Technical review process: Technical committee and supervisors complete preliminary review=within 48 hours, checking proposal technical completeness and potential risks. If serious issues are found, they can suggest proposers voluntarily withdraw.
On-chain voting (3-7 days, depending on proposal type)
Voting duration setting: Lightweight proposals 3 days, standard proposals 5 days, major proposals 7 days. This differentiated design balances decision efficiency with the need for sufficient discussion.
Voting option settings: Each voter can choose ”Support,” ”Oppose,” or ”Abstain.” Abstention votes count toward participation rate but don’t affect support rate calculation, allowing voters to express ”participation without stance.”
Cooling period setting: Passed proposals automatically enter cooling periods (lightweight 24 hours, standard 48 hours, major 72 hours), reserving time for potential problem discovery and emergency response.
Final security check: Supervisors conduct final security checks during the cooling period. If previously undiscovered serious issues are found, they can extend the cooling period or request community reconsideration through multi-sig mechanisms.
Automatic execution trigger: After the cooling period ends, governance contracts automatically execute proposal content. For parts requiring off-chain cooperation, authorize relevant execution teams to implement according to proposal requirements.
