Compound Governance is the on-chain process through which holders of COMP and their delegates propose, vote on, and carry out changes to the Compound protocol. The system uses contracts such as a governor and a Timelock; the exact proposal rules and execution path depend on the Compound version and its current configuration.
What governance can change
Compound governance is an administrative layer. In Compound v2, approved proposals can call protocol functions to change supported markets, parameters, or other contract behavior. Compound III uses governance to control administrative components such as proxies, the Configurator, the Comet factory, and Comet implementations. A governance vote does not decide each individual supply or borrow transaction; it can change the rules and contracts those transactions use.
Proposals specify actions for the protocol contracts to execute. Readers should distinguish a proposal’s discussion and vote from its execution: an approved result may still need to pass through a Timelock or other configured execution steps before it changes a market.
From delegation to execution
COMP holders can delegate voting power to themselves or to another address. Delegation assigns voting weight; it does not transfer ownership of the COMP. A delegate can participate in proposals using the voting power assigned to that address.
In the documented Compound v2 design, Governor Bravo manages proposals and voting, while a Timelock queues approved actions for later execution. This delay separates the vote from implementation and gives participants time to inspect the proposed contract calls. Compound III documentation describes governance proposals that can configure markets and, for some implementation changes, deploy and activate a new Comet implementation.
Proposal thresholds, quorum rules, voting periods, and delays are contract parameters and can change. A historical description or a fixed number copied from an old guide should not be treated as the current rule for every Compound market. Check the live proposal and current protocol documentation when a specific threshold or execution schedule matters.
Compound v2 and Compound III
Compound v2 documentation identifies COMP, Governor Bravo, and the Timelock as the main governance components. Proposals can call administrative functions associated with the v2 markets and Comptroller.
Compound III also uses COMP-holder and delegate governance, but its market contracts have a different architecture. The official documentation describes the Timelock as an administrator for Compound III instances and explains how governance can update Configurator settings or deploy a new Comet implementation. Deployments on other chains also rely on chain-specific receivers and local Timelocks to carry out approved changes.
What governance does not guarantee
On-chain voting makes proposal actions and votes observable, but it does not mean every user participates or that voting power is evenly distributed. COMP voting power is delegated token weight, so a vote measures that weight rather than a one-person-one-vote count. A Timelock creates a review interval; it does not by itself prove that a proposal is safe or that participants will notice a problem.
Related Terms
See Also
- Why DAO Governance Votes Often Fall Short — and Why Protocols Still Use Them
- Why Smart Contract Audits Fail: What Post-Mortems Reveal About the Limits of Security Reviews
- What Is Tokenomics — And Why It Determines Whether a Crypto Project Survives
Sources
- Compound v2 Governance Documentation — Describes COMP delegation, Governor Bravo, proposal voting, and the Timelock’s role in executing approved changes.
- Compound III Governance Documentation — Documents COMP-holder governance and the administrative contracts and deployment steps used by Compound III.
- Analyzing Voting Power in Decentralized Governance: Who Controls DAOs? — Empirically studies voting-power distribution and participation in Compound, Uniswap, and ENS governance systems.