MAGNE’s decentralized governance system empowers $MHA token holders to steer protocol-level changes including Reward Vault approvals, native dApp configurations, and PoW distribution logic.
MAGNE’s governance is based on OpenZeppelin’s battle-tested contracts, providing a secure and transparent multi-phase lifecycle:
Proposal Creation
Any account with sufficient voting power may initiate a proposal
Pending State
Proposals enter a brief 1-hour delay before becoming active for voting
Voting Phase
$MHA holders (or their delegates) can cast votes during the 5-day voting window
Proposal Outcome
If quorum and majority thresholds are met, the proposal is marked as Succeeded
Timelock Queue
Successful proposals enter a 2-day delay queue before execution
Execution
Once timelock elapses, the change can be implemented on-chain by any actor
To protect the protocol from malicious behavior, MAGNE uses a 5-of-9 Guardian Council with the authority to cancel dangerous proposals during the timelock phase (e.g., unauthorized upgrades or asset seizure).
Ensure You Meet the Voting Threshold
You need at least 10,000 $MHA worth of delegated voting power
Delegate to Yourself
You must explicitly delegate $MHA (even to yourself) to unlock governance rights
Prepare the Proposal Payload
For example, a Reward Vault proposal must include the vault address and correct function call (e.g., addRewardVault(address))
Submit the Proposal
Submit through the on-chain governance contract or via the MAGNEHub UI
Promote the Proposal
Engage the community to build awareness and gather votes
Execute After Timelock
If passed, any user can trigger execution after the 2-day delay
| State | Criteria |
|---|---|
| Proposal Creation | 10,000 $MHA delegated votes |
| Pending Period | 1 hour |
| Voting Period | 5 days |
| Quorum Threshold | 20% of total $MHA supply |
| Timelock Delay | 2 days |
Reward Vault proposals may follow a simplified governance path. See the Reward Vault Governance Docs for details.