Governor Bravo vs OpenZeppelin Governor Architecture

Frequently Asked Questions

01.What is the difference between Governor Bravo and OpenZeppelin Governor?

Governor Bravo is Compound's governance contract, an upgradeable successor to GovernorAlpha deployed behind a delegator proxy so its logic can change without migrating state. OpenZeppelin Governor is a modular framework that achieves the same governance lifecycle through Solidity inheritance rather than a monolithic contract, and it ships a GovernorCompatibilityBravo module for Bravo-style interfaces. Bravo is a specific battle-tested deployment, while OpenZeppelin Governor is a configurable system you compose from modules.

02.How does the propose, queue, execute lifecycle work?

A proposal is created with propose, then enters a voting delay before voting opens. Token holders cast votes across a voting period, and if the proposal reaches quorum and passes, it moves to queue, which schedules it in a timelock contract. After the timelock delay elapses, execute runs the proposal's calls. The timelock holds the governed assets and enforces the delay, giving the community a window to react before any change takes effect.

03.

04.Why does a governance system need a timelock?

A timelock inserts a mandatory delay between a proposal passing and its execution, so the contract that actually holds and moves the governed assets only acts after that delay. This window lets token holders who disagree with a passed proposal exit or organise before it takes effect, which is the main defence against a malicious or rushed proposal. Both Governor Bravo and OpenZeppelin Governor execute through an external timelock for this reason.