> For the complete documentation index, see [llms.txt](https://gitbook.raac.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.raac.io/learn/usdraac-token/usdveraac/utility.md).

# Utility

&#x20;$veRAAC holders govern the protocol, direct value flows, and benefit from revenue sharing. They receive:

* 80% of platform fees and 25% of both REET NFT royalties and $RAAC token tax (described in more detail in the “[Protocol Economics & Fees](https://gitbook.raac.io/learn/overview/protocol-economics-and-fees.md)” section)&#x20;
* Direct $RAAC ecosystem distributions and RWA yield via a dual gauge system.
* Boosted emissions
* Governance rights

As RAAC expands, $veRAAC holders will participate in every vertical. Revenue from all RWAs tokenized in the RAAC ecosystem, whether from silos or RAACLend, will flow to RAAC.


---

# 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://gitbook.raac.io/learn/usdraac-token/usdveraac/utility.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.
