> 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/xvs/xvs-vault-treasury.md).

# XVSVaultTreasury

`XVSVaultTreasury` receives XVS allocated by the protocol-reserve conversion flow and funds the XVSStore used by an XVS Vault.

## BNB deployment

At BNB Chain block `118,364,540`:

| Field                  | Value                                        |
| ---------------------- | -------------------------------------------- |
| Proxy                  | `0x269ff7818DB317f60E386D2be0B259e1a324a40a` |
| Implementation         | `0xA95a4f34337d8fAC283c3e3D2A605b95dA916cD6` |
| Owner                  | `0x939bD8d64c0A9583A7Dcea9933f7b21697ab6396` |
| Access Control Manager | `0x4788629ABc6cFCA10F9f969efdEAa1cF70c23555` |
| XVS Vault              | `0x051100480289e704d20e9DB4804837068f3f9204` |
| XVS                    | `0xcF6BB5389c92Bdda8a3747Ddb454cB7a64626C63` |

Other network deployments can use different proxies, implementations, owners, and vaults.

## API and permissions

```solidity
constructor(address xvsAddress_)
function initialize(address accessControlManager_, address xvsVault_) public
function setXVSVault(address xvsVault_) external
function fundXVSVault(uint256 amountMantissa) external
function sweepToken(address tokenAddress, address to, uint256 amount) external
```

* `setXVSVault` is `onlyOwner`.
* `fundXVSVault` checks `fundXVSVault(uint256)` through the Access Control Manager and sends XVS directly to the vault's current XVSStore.
* `sweepToken` is `onlyOwner`; it is **not** gated by the Access Control Manager.

Because this contract holds funds and can change its destination vault, resolve the live proxy implementation, owner, ACM permissions, and `xvsVault()` value before an operator transaction.

Source: [XVSVaultTreasury.sol](https://github.com/VenusProtocol/protocol-reserve/blob/main/contracts/ProtocolReserve/XVSVaultTreasury.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 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-core-pool/vaults/xvs/xvs-vault-treasury.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.