Governor Bravo
- Name: Governor Bravo
- URL: https://docs.compound.finance/v2/governance/
- Category: token-governance execution framework / timelocked proposal system / Compound-style governance baseline
- Summary: Governor Bravo is worth cataloging not as a generic DAO-contract footnote or just a historical Compound implementation detail, but as one of the canonical onchain governance baselines that later DAO tooling keeps targeting, extending, or working around. Its primary materials make the core mechanism explicit: delegated token voting with snapshot-based vote accounting, proposal thresholds, bounded batched actions, a timelock queue before execution, and admin-adjustable governance parameters inside defined ranges. The reusable insight is that governance authority here is not only in token balances. It also sits in proposal thresholds, quorum rules, action batching limits, timelock delay, cancellation conditions, whitelist pathways, and the upgradeable delegator/delegate contract split. That makes Governor Bravo a useful comparison point for Seatbelt, ScopeLift, OpenZeppelin-style governors, and any DAO stack that claims to decentralize control while inheriting a very specific token-vote-plus-timelock policy machine.
- What it does:
- Lets delegated COMP voting power create, vote on, queue, and execute proposals that call administrative functions on protocol contracts
- Uses
getPriorVotessnapshots so voting power is measured from a prior block rather than a live balance during the vote - Batches up to 10 ordered actions into one proposal for later execution through a timelock
- Separates proposal success from proposal execution by requiring successful proposals to be queued and delayed before execution
- Restricts proposers to one live proposal at a time and allows cancellation if a proposer falls below threshold or other guarded conditions apply
- Exposes governance parameters such as voting period, voting delay, and proposal threshold within bounded ranges, making the governance machine itself governable
- Uses an upgradeable delegator/delegate pattern and includes whitelist/guardian machinery, which means administrative authority is more layered than a simple
token votestory suggests
- Key claims:
- Compound’s governance docs identify Governor Bravo as the governance module alongside COMP and the Timelock, which is the clearest first-party framing for why this contract deserves its own note.
- The docs say tokenholders with delegated voting power above the proposal threshold can propose, that voting uses prior votes, and that successful proposals are queued in the Timelock before later execution. That queue-before-execute split is the durable policy mechanism here.
- The contract source makes several hidden control surfaces explicit: fixed quorum votes, a maximum of 10 actions per proposal, bounded parameter ranges for voting period/delay/threshold, and a one-live-proposal-per-proposer rule.
- The source also shows that proposal power is not purely token-native. Whitelisted proposers and a
whitelistGuardianexist, which means there is a policy escape hatch alongside standard vote thresholds. - The proposal and receipt structs are analytically useful because they preserve not just yes/no voting but the full action bundle, start/end blocks, queue ETA, and per-voter receipts. Governor Bravo is therefore a governance execution pipeline, not merely a voting counter.
- Governor Bravo belongs in the corpus because many later governance safety and tooling systems are really downstream responses to this exact design shape: token delegation, proposal batching, timelock delay, and execution through privileged contract calls.
- Whitepaper: No standalone Governor Bravo whitepaper surfaced in this pass. The strongest primary materials were Compound’s governance docs and the official contract sources reviewed in
../../whitepapers/governor-bravo-primary-sources-2026-05-19.md. - Sources:
Internal linkages
-
Keep this on the cleanest governance-execution contrasts: seatbelt, threshold-network, and molochdao.
-
Last reviewed: 2026-06-05 UTC