> For the complete documentation index, see [llms.txt](https://docs.bio.xyz/bio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bio.xyz/bio/descientists/about-bio-assets/vebio.md).

# veBIO

## What is veBIO?

veBIO stands for "vote-escrowed BIO" and represents your governance power within the Bio Protocol. It is not a transferable token but rather a status that grants you voting rights and a greater share of protocol rewards. The longer you lock your BIO, the more veBIO you receive.

## How to get veBIO?

You can obtain veBIO by staking your BIO tokens in the protocol's governance module:

1. **Acquire $BIO**: First, ensure you have BIO in your wallet.
2. **Navigate to the Staking Page**: Go to the official staking interface on the Bio.xyz platform.
3. **Choose Lock-up Period**: Select the amount of BIO you wish to stake and the duration you want to lock it for. The longer the lock-up period, the more veBIO you will receive in return.
4. **Confirm Transaction**: Approve the transaction in your wallet to lock your $BIO and receive veBIO.

For more information, refer to our guide on [Staking BIO](/bio/introduction/bio-protocol-v2/staking-and-vebio/staking-bio.md)

## How to use veBIO?

veBIO is used to actively participate in the governance and direction of the Bio Protocol:

* **Voting on Proposals**: Use your veBIO to vote on key governance proposals, such as funding decisions, protocol upgrades, and parameter changes.
* **Earning Boosted Rewards**: Holding veBIO can boost your yield from staking and other reward-generating activities.
* **Signaling and Curation**: Influence which projects or BioAgents receive attention and a greater share of resources from the ecosystem.

***

## Further Reading

For more detailed information about veBIO and its role in the ecosystem, please see the following pages:

* [**Staking BIO**](/bio/introduction/bio-protocol-v2/staking-and-vebio/staking-bio.md): A step-by-step guide on how to stake your `BIO` tokens to obtain `veBIO`.

## Related Information

**Token Information:**

* [**$BIO Token Guide**](/bio/descientists/about-bio-assets/bio.md) - How to acquire and use the native BIO token
* [**BioXP Guide**](/bio/descientists/about-bio-assets/bioxp.md) - Understanding the points system and earning mechanics
* [**All Assets Overview**](/bio/descientists/about-bio-assets.md) - Complete overview of ecosystem tokens

**Staking & Governance:**

* [**Staking & veBIO Overview**](/bio/introduction/bio-protocol-v2/staking-and-vebio.md) - Complete staking system guide
* [**Staking Other Assets**](/bio/introduction/bio-protocol-v2/staking-and-vebio/staking-other-assets.md) - Alternative staking strategies
* [**Launchpad FAQ**](/bio/introduction/bio-protocol-v2/launchpad-faq.md) - Common questions about veBIO and governance


---

# 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.bio.xyz/bio/descientists/about-bio-assets/vebio.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.