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

# Token Utility

Anything on this page is subject to change throughout the development progress of the game. We will thoroughly test and validate any feature before it goes live.

$SV serves as the glue that binds the entire ecosystem together through:

* **Governance**: Holders participate in ecosystem decisions.
* **Incentives & Rewards**: Distribution to NFT holders, token stakers, and game participants.
* **Transactions & Fees**: Used for in-game purchases, marketplace transactions, and ecosystem services.
* **Staking & Yielding**:
* *NFT Holders*: Earn rewards for staking their SHODO VEIL NFTs.
* *Token Holders*: Stake $SV to earn periodic yield.
* **Incentive Distribution**: A portion of ecosystem revenues is distributed back to the community in $SV.
* **IP Expansion Support**: Funding for media, merchandise, and entertainment projects under SV Labs.


---

# 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://shodo-veil.gitbook.io/whitepaper/economics/token-utility.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.