> For the complete documentation index, see [llms.txt](https://docs.yo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yo.xyz/user-guides/usdyo-token.md).

# $YO Token

#### WHAT IS $YO?

#### Governance with Purpose

$YO is more than just another governance token. It represents a stake in shaping the engine that powers the future of decentralized yield. Holding $YO will give you a direct vote on key decisions around the protocol including future initiatives to grow the YO ecosystem and adjustments to vault parameters.

#### Sustainable Yield Infrastructure

The YO Protocol introduces a sustainable yield model with tokenized vaults like yoUSD, yoETH, yoEUR, yoBTC, and yoGOLD. Each vault operates through algorithmic, predefined parameters to generate stable and predictable returns for users.

#### Decentralization by Design

After TGE, token holders can participate in guiding the protocol's future direction. In the initial phase, governance will be guided by the team, with community feedback. As YO's decentralization roadmap is executed, control will progressively transition to token holders until governance is fully onchain.

{% embed url="<https://app.yo.xyz/tokenomics>" %}

#### REWARDS PROGRAM: HOW TO EARN $YO

**Deposit into YO Vaults**

Choose between yoUSD, yoETH, yoEUR, yoBTC, yoUSD Edge or yoGOLD vaults and start earning base yield plus additional $YO rewards.

**Participate in DeFi activities**

Add liquidity to all of our supported DeFi activities to earn $YO rewards. You can see available opportunities [directly in-app](https://app.yo.xyz/rewards).&#x20;

$YO will launch with an initial non-transferable phase, where claimed tokens cannot be sold, traded, or transferred to another wallet. This phase is designed to ensure that $YO is widely held by active users and contributors who align with the long-term success of the ecosystem.

**Claiming $YO**

All $YO rewards are distributed via [Merkl](https://app.merkl.xyz/protocols/yo?tokenType=all\&sort=tvl-desc), and can be claimed [directly in-app](https://app.yo.xyz/rewards) or via Merkl's UI. Regardless of where you deposit, all claims of $YO happen on Base chain exclusively.&#x20;

Each month, $YO reward campaigns are published to incentivize deposits into YO vaults or into specific DeFi activities. Campaigns are time-bounded and all users that participate in the specific activity qualify for earning $YO rewards, which have to be claimed. [As per the Terms and Conditions](https://www.yo.xyz/terms-of-service), YO Foundation may claw back any unclaimed tokens 6 months after the expiration of each campaign, to be distributed again in future campaigns.&#x20;


---

# 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.yo.xyz/user-guides/usdyo-token.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.
