> For the complete documentation index, see [llms.txt](https://docs-v4.venus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.venus.io/technical-reference/reference-governance.md).

# Governance

These references cover several deployed generations. They are not one interchangeable ABI. The source baseline for this section is the stable [`governance-contracts` v2.15.0 tag](https://github.com/VenusProtocol/governance-contracts/tree/v2.15.0).

| Family               | Production role                                                                                 | Version boundary                                                                                                                                                                              |
| -------------------- | ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Governor Bravo       | Proposes, votes, queues, and executes BNB Chain VIPs through three route-specific timelocks     | Upgradeable Solidity 0.5 governor. Its V1 scalar `votingDelay`, `votingPeriod`, and `proposalThreshold` slots are deprecated; current rules are stored per proposal type in `proposalConfigs` |
| Omnichain governance | Sends approved BNB Chain commands to executors and TimelockV8 contracts on destination networks | LayerZero V1-style messaging with `uint16` endpoint IDs (called chain IDs in the ABI). Do not substitute EVM chain IDs or LayerZero V2 EIDs/OApp APIs                                         |
| Risk Steward V2      | Publishes and validates bounded risk-parameter updates                                          | Current stable source, but rollout is not uniform: v2.15.0 artifacts contain the BNB mainnet origin stack and destination receivers/stewards on testnets, not on every destination mainnet    |
| Access control       | Resolves exact-contract and wildcard function-signature permissions                             | The BNB mainnet AccessControlManager has the older ABI without `hasPermission`; the seven destination-mainnet artifacts include it                                                            |

`AccessControlledV5` remains relevant to live legacy contracts. `AccessControlledV8` is the current Solidity 0.8 base, but inherited owner, proxy, and access-control selectors depend on the exact deployed implementation.

LayerZero labels V1 deprecated for new integrations in its [V1 deployment reference](https://docs.layerzero.network/v1/deployments/deployed-contracts). That upstream lifecycle label does not mean the active Venus Omnichain Governance contracts have been retired; it means new code must not silently substitute V2 APIs for this legacy transport.

Addresses and lifecycle labels belong in the [deployed governance registry](/deployed-contracts/governance.md). Use this section for ABI and version selection, and identify a proxy's implementation before encoding administrative calls.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs-v4.venus.io/technical-reference/reference-governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.