> 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-core-pool/vaults/vai/vai-vault-proxy.md).

# VAIVaultProxy

`VAIVaultProxy` is a custom delegate proxy. Users and integrations call the proxy; state is stored at the proxy while the implementation supplies logic.

## BNB deployment

At block `118,364,540`:

| Field                             | Address                                      |
| --------------------------------- | -------------------------------------------- |
| Proxy                             | `0x0667Eed0a0aAb930af74a3dfeDD263A73994f216` |
| `vaiVaultImplementation()`        | `0xA52f2a56aBb7cbDD378bC36c6088fAfEaf9AC423` |
| `admin()`                         | `0x939bD8d64c0A9583A7Dcea9933f7b21697ab6396` |
| `pendingVAIVaultImplementation()` | Read live before an upgrade                  |
| `pendingAdmin()`                  | Read live before an admin transfer           |

The constructor initially sets `admin` to the deployer. The current admin can call `_setPendingImplementation(address)` and `_setPendingAdmin(address)`. A pending implementation or admin must accept its role through `_acceptImplementation()` or `_acceptAdmin()` respectively.

These methods return protocol error codes: `0` means success. Decode the return value and emitted events instead of relying only on EVM transaction success.

Source: [VAIVaultProxy.sol in venus-protocol v10.3.0](https://github.com/VenusProtocol/venus-protocol/blob/v10.3.0/contracts/VAIVault/VAIVaultProxy.sol).


---

# 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-core-pool/vaults/vai/vai-vault-proxy.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.