> 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/governor-bravo-interfaces.md).

# GovernorBravoInterfaces

## GovernorBravoEvents

Storage structures and events used by the stable [`GovernorBravoInterfaces.sol` v2.15.0 source](https://github.com/VenusProtocol/governance-contracts/blob/v2.15.0/contracts/Governance/GovernorBravoInterfaces.sol).

The V1 scalar `votingDelay`, `votingPeriod`, `proposalThreshold`, and `timelock` storage slots are explicitly deprecated in the source but retained for upgrade-safe layout. Current logic uses the V2 `proposalConfigs` and `proposalTimelocks` mappings, plus the V3 `validationParams` structure.

## Solidity API

```solidity
struct Proposal {
  uint256 id;
  address proposer;
  uint256 eta;
  address[] targets;
  uint256[] values;
  string[] signatures;
  bytes[] calldatas;
  uint256 startBlock;
  uint256 endBlock;
  uint256 forVotes;
  uint256 againstVotes;
  uint256 abstainVotes;
  bool canceled;
  bool executed;
  mapping(address => struct GovernorBravoDelegateStorageV1.Receipt) receipts;
  uint8 proposalType;
}
```

```solidity
struct Receipt {
  bool hasVoted;
  uint8 support;
  uint96 votes;
}
```

```solidity
enum ProposalState {
  Pending,
  Active,
  Canceled,
  Defeated,
  Succeeded,
  Queued,
  Expired,
  Executed
}
```

```solidity
enum ProposalType {
  NORMAL,
  FASTTRACK,
  CRITICAL
}
```

```solidity
struct ProposalConfig {
  uint256 votingDelay;
  uint256 votingPeriod;
  uint256 proposalThreshold;
}
```

```solidity
struct ValidationParams {
  uint256 minVotingPeriod;
  uint256 maxVotingPeriod;
  uint256 minVotingDelay;
  uint256 maxVotingDelay;
}
```

#### proposalCount

The total number of proposals

```solidity
function proposalCount() external returns (uint256)
```

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.