> 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-oracle/correlated-token-oracles/bnbx-oracle.md).

# BNBxOracle

[`BNBxOracle`](https://github.com/VenusProtocol/oracle/blob/v2.16.0/contracts/oracles/BNBxOracle.sol) calls the immutable Stader StakeManager to convert one BNBx into BNB, then applies the ResilientOracle BNB price. It inherits the [capped V2 base](/technical-reference/reference-oracle/correlated-token-oracles/correlated-token-oracle.md).

```solidity
constructor(
    address stakeManager,
    address bnbx,
    address resilientOracle,
    uint256 annualGrowthRate,
    uint256 snapshotInterval,
    uint256 initialSnapshotMaxExchangeRate,
    uint256 initialSnapshotTimestamp,
    address accessControlManager,
    uint256 snapshotGap
)
```

The BNB mainnet v2.16.0 artifact is the non-proxy contract `0xC2E2b6f9CdE2BFA5Ba5fda2Dd113CAcD781bdb31`. At block `118367342`, its snapshot interval was `2,592,000` seconds, its growth rate was `2,387,747,336` per second, its gap was `6,956,741,073,522,234`, and `isCapped()` returned false.

`STAKE_MANAGER()` exposes the immutable Stader dependency, and `NATIVE_TOKEN_ADDR()` exposes the BNB pricing sentinel. These values, token addresses, and cap configuration are instance-specific; do not reuse them from another BNB-correlated oracle.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs-v4.venus.io/technical-reference/reference-oracle/correlated-token-oracles/bnbx-oracle.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 `build a script that syncs our docs to a CMS` 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.