# Open Zeppelin Governor ### Summary: * Open Zeppelin utilizes the Compound Governor framework, but with a few added features to improve flexibility. ### **Key Changes Versus Compound Governor:** * Modular design and architecture to minimize protocols' need to fork components * Ability to meet protocol specific requirements with addition of small modules using solidity inheritance * Minimized use of storage improves gas efficiency * Two versions of components: one optimized for efficiency, with another designed for optional compatibility with Compound Governor contracts ![](https://cdn.document360.io/5b297d02-8aa1-4075-baa1-d431b2292be1/Images/Documentation/image%2818%29.png) ### **Resources:** * [Announcement post](https://blog.openzeppelin.com/governor-smart-contract/) * [Open Zeppelin Forum](https://forum.openzeppelin.com/) * [Open Zeppelin Governor Github](https://github.com/OpenZeppelin/openzeppelin-contracts/tree/master/contracts/governance) * [Open Zeppelin Governor docs](https://docs.openzeppelin.com/contracts/4.x/api/governance) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.common.xyz/commonwealth/community-overview-2/governance/what-is-decentralized-governance/governance-frameworks/open-zeppelin-governor.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.