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

# $RIVUS Tokenomics

## $RIVUS V2 Tokenomics

<div data-full-width="true"><figure><img src="/files/dVQCIVIuhF08krlXVzjR" alt=""><figcaption></figcaption></figure></div>

The Rivus V2 Tokenomics has greatly improved to allow for retained stability for the $RIVUS token in addition to utilizing our treasury to redirect rewards over to our holders. By doing so, we're expecting the protocol to revolve around the $RIVUS token and by nature grow the TVL of all our rsAssets.

To tie everything together, the 10% Protocol Fee will be used to buyback $RIVUS and either hold it in our treasury/liquidity incentive or burn the supply. This will help bring value to the governance token, $RIVUS.

**Total Supply: 1,000,000,000 $RIVUS**

<figure><img src="/files/HneldVqzBPnpgDNXGgEk" alt=""><figcaption></figcaption></figure>

Buy/Sell = 5/5

* the buy and sell fees will be utilized to bolster treasury and will also enable us to provide further growth for our holders.

40% V1 Migration

* Please refer to our prior V1 token economics here (<https://docs.rivusdao.xyz/usdrivus-token/usdrivus-tokenomics>)

35% Deflationary Incentives

* We will be utilizing daily token burns from our V2 supply in order to create deflation on our V2 Tokenomics. Burns will be done but its not limited to redemption of staked $RIVUS

9% V2 Liquidity

* This will be used for the V2 $RIVUS LP pool.

9% Sablier

* The sabler is the continued vesting of our early supporters from V1.

7% Team / CEX

* 5% is the team and 2% is the CEX with the original vesting schedules from V1.


---

# 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.rivusdao.xyz/usdrivus-token/usdrivus-tokenomics.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.