Governance Framework
Dubhe OpenGov Governance
4.1 Design Goals
- Fully On-chain: All decisions executed natively on DubheOS, no off-chain approval.
- Risk Stratification: 7 parallel “Tracks” based on proposal impact.
- Time-for-Conviction: Conviction Voting rewards longer lock-in with higher vote weight.
- Efficient & Transparent: Emergency upgrades in 12 hours; major changes in 28 days max.
4.2 Parallel Tracks
| Track | Examples | Max in Parallel | Vote Duration | Timelock |
|---|---|---|---|---|
| Root | Runtime upgrades, protocol params | 1 | 7d | 14d |
| Treasury-L | >$20k Treasury Spend | 2 | 5d | 7d |
| Treasury-S | ≤$20k Grants/Bounties | 5 | 3d | 2d |
| Param-Fast | Emergency fixes, gas caps | 3 | 12h | 12h |
| Param-Std | Chain param changes | 5 | 3d | 2d |
| Tip/Bounty | Micro community rewards | 15 | 2d | 1d |
| Builder Refund | Dev bond refunds | 10 | 2d | 1d |
All tracks use Adaptive Quorum — the closer to deadline, the closer the threshold to 50%.
4.3 Conviction Voting Multipliers
| Lock Multiplier | Actual Lock Time | Vote Weight |
|---|---|---|
| 0Ă— | 0 days | 1Ă— |
| 1Ă— | 14 days | 2Ă— |
| 2Ă— | 1 month | 3Ă— |
| 4Ă— | 2 months | 4Ă— |
| 8Ă— | 4 months | 5Ă— |
| 16Ă— | 8 months | 6Ă— |
4.4 Governance Flow
Submit → Lead-in (Threshold Check) → Vote → Confirm → Timelock → On-chain Execution
- Lead-in: Must meet minimum support before voting.
- Vote: Users can add weight or change votes during period; proposal fails if “Kill Threshold” is met.
- Timelock: Root = 14d; others = 12h–7d.
4.5 Treasury Management
- Treasury Address:
0xDUBHETreasurySafe— 5/9 multisig, executes approved proposals only. - Revenues: 33.33% of fees, unclaimed rewards, MEV premiums.
- Spending: Any address may submit; >$20k requires Treasury-L, including audit & KPI proof.
4.6 Safety & Emergency
| Scenario | Trigger | Max Execution Time |
|---|---|---|
| Consensus bug hotfix | Param-Fast Track | 24h |
| Lock contract failure | Root Fast Track + â…” YES | 12h |
| Multisig key leak | DAO proposal to rotate | 24h |
4.7 Governance Participation
- Lock: Choose multiplier on Dubhe Portal → get voting weight.
- Propose: Upload metadata (GitHub/IPFS) → pick Track → deposit refundable bond.
- Vote: Sign via wallet or Passkey / zkLogin; add weight or flip votes anytime.
- Track: Governance Dashboard shows proposal statuses, countdowns, approval trends.
Incentives: 2% of Builders Bonus + Community Incentives each quarter is awarded to active voters by weight.
Dubhe OpenGov is scheduled to go live with DubheOS Beta in Q1 2026. Governance parameters may be adjusted after 6 months of mainnet operation.