> 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/stk-bnb-oracle.md).

# StkBNBOracle

The currently registered BNB mainnet StkBNBOracle is an **uncapped V1 transparent proxy**, not an instance of the capped repository-main source.

| Checked block | Proxy                                        | Implementation                               |
| ------------: | -------------------------------------------- | -------------------------------------------- |
|   `118367342` | `0xdBAFD16c5eA8C29D1e94a5c26b31bFAC94331Ac6` | `0xA7C432c50D310c805c8342488921A108b585397F` |

The implementation constructor is:

```solidity
constructor(
    address stakePool,
    address stkBNB,
    address resilientOracle
)
```

`getUnderlyingAmount()` reads the StakePool exchange-rate structure, rejects a zero pool-token supply, and returns BNB per stkBNB. `getPrice(stkBNB)` multiplies that amount by the ResilientOracle BNB price.

The V1 implementation exposes immutable `STAKE_POOL`, `CORRELATED_TOKEN`, `UNDERLYING_TOKEN`, `RESILIENT_ORACLE`, and `NATIVE_TOKEN_ADDR` getters. It does not expose the V2 snapshot/growth setters.

The [`StkBNBOracle.sol` file at v2.16.0](https://github.com/VenusProtocol/oracle/blob/v2.16.0/contracts/oracles/StkBNBOracle.sol) has the newer nine-argument capped V2 constructor. Do not use that ABI for the proxy above unless a later onchain implementation upgrade proves it applies.


---

# 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-oracle/correlated-token-oracles/stk-bnb-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 `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.