Skip to main content

26. Governance

26.1 On-Chain Governance​

The repository contains governance-related contract and policy components, but it does not establish a complete, activated and audited on-chain governance system for the Quantos protocol. Proposal authority, voting asset, delegation, timelocks, upgrade keys and treasury control must be fixed by the network configuration and deployed governance contracts.

26.2 Proposal Lifecycle​

The intended governance design follows a standard lifecycle, subject to implementation and deployment validation:

  1. Proposal — a staked participant submits a proposal (a parameter change, treasury disbursement, or upgrade authorisation).
  2. Voting — QTS holders vote within a fixed window; voting power is stake-weighted, and delegation behavior would depend on the deployed governance and staking implementation.
  3. Quorum & threshold — a proposal passes only if it meets both a participation quorum and an approval threshold, preventing low-turnout capture.
  4. Timelock — an approved proposal enters a timelock delay before execution, giving the network time to react (including exiting) if a malicious proposal somehow passes.
  5. Execution — after the timelock, the change is enacted on-chain.

26.3 What Governance Controls​

A future governance system may control selected economic, sharding, treasury and upgrade parameters. The current repository does not define a canonical authority, quorum, voting period, timelock, delegation model or immutable safety boundary. Those values must be published before governance claims are made.

26.4 Treasury and Public Goods​

A future governance deployment could direct protocol-controlled funds to a treasury for audits, tooling, grants and ecosystem development. The current repository does not establish a live revenue split, treasury balance, or independent DAO control.

26.5 Quantum-Safe Governance​

Governance transactions use whatever signing and execution path is active in the deployed node. The current ordinary signing implementation uses ML-DSA-65. Governance security therefore remains conditional on the concrete account, contract, key-management and upgrade paths.