> For the complete documentation index, see [llms.txt](https://gitbook.weave.financial/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.weave.financial/product-docs/tokenomic/usdweave-token/weave-token-use-cases.md).

# Weave token use cases

Our native crypto asset is the $Weave token. $Weave can be earned as bonus rewards by users of the platform and for staking or providing liquidity for the $Weave token.

Use cases for the $Weave token include;

* Governance - staking/LP providers can vote on strategic decisions
* Reducing platform fees - a sliding scale of fees based on amount staked 
* Awarded to users for using the dApp and for staking & LP for the $Weave token 
* Staking/LP providers receive a share of platform fees
* Staking/LP providers receive % of all $Weave token sales
* Staking/LP Providers will soon unlock additional platform features & tools 
* Referral/Affiliate program requires staking or LP to unlock higher earning levels

\
\ <br>


---

# 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://gitbook.weave.financial/product-docs/tokenomic/usdweave-token/weave-token-use-cases.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.