> 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/tokens/xvs.md). # XVS XVS is the governance token of Venus Protocol. Holders can deposit XVS in the XVS Vault, delegate the associated voting power, and participate in Venus Improvement Proposals (VIPs). Staking alone does not make voting power active: the vault position must be delegated to the holder's address or another delegate. A proposal uses the delegate's voting-power snapshot at its start block. Delegation does not transfer ownership of the staked XVS. See [Delegating and Voting](/guides/governance/delegating.md) for the participation workflow and [Venus Improvement Proposals](/governance/decentralization.md) for current governance rules. ## Vault rewards The XVS Vault can distribute governance-funded base rewards and XVS purchased with protocol revenue. Reward funding and emission speed are configurable and may change through VIPs. Staking XVS therefore does not guarantee a particular yield. See [Tokenomics](/governance/tokenomics.md) for the current policy snapshot and instructions for checking the live reward speed. ## Venus Prime An XVS Vault position also contributes to [Venus Prime](/whats-new/prime-yield.md) eligibility. Prime uses a time-weighted leaderboard that considers both the amount and age of eligible XVS stakes. At each configured issuance epoch, governance can issue a limited number of non-transferable Prime tokens to qualifying accounts. Leaderboard rank does not guarantee issuance, and the epoch schedule, token limit, minimum stake, and other conditions are governance-configurable. Check the current Prime interface and deployed configuration before relying on a particular eligibility rule. --- # 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/tokens/xvs.md?ask=&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.