> 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-store.md).

# XVSStore

XVSStore holds reward tokens and transfers them on behalf of its configured owner, normally an XVS Vault. It is a non-proxy contract with separate `admin` and `owner` roles.

{% hint style="warning" %}
Every network has its own store, roles, balances, and active reward-token list. Read those values from the exact address in [Deployed Funds](/deployed-contracts/funds.md).
{% endhint %}

## Roles and API

| Function                                      | Caller requirement | Effect                                                                    |
| --------------------------------------------- | ------------------ | ------------------------------------------------------------------------- |
| `safeRewardTransfer(address,address,uint256)` | Owner              | Transfers an active reward token, capped by the store's available balance |
| `setPendingAdmin(address)`                    | Admin              | Starts an admin transfer                                                  |
| `acceptAdmin()`                               | Pending admin      | Accepts the admin role                                                    |
| `setNewOwner(address)`                        | Admin              | Replaces the owner that can distribute or withdraw rewards                |
| `setRewardToken(address,bool)`                | Admin **or owner** | Enables or disables a reward token                                        |
| `emergencyRewardWithdraw(address,uint256)`    | Owner              | Withdraws a reward token from the store                                   |

The owner can therefore both distribute active rewards and change which tokens are active. The admin can replace the owner. Permission reviews must account for both roles rather than treating the vault as the only privileged actor.

Source: [XVSStore.sol in venus-protocol v10.3.0](https://github.com/VenusProtocol/venus-protocol/blob/v10.3.0/contracts/XVSVault/XVSStore.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/xvs/xvs-store.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.