# Tokenomics

***

## Protocol Revenues

* **Real-World Asset Backing**: One of the primary revenue models involves backing T-REX tokens with real-world assets (RWA) generating yield and capital gains. By assisting projects in launching their tokenized assets, the DAO can invest in these projects and receive tokenized assets in return. This approach transforms T-REX into a decentralized cooperative for RWA, providing a robust and tangible backing for the T-REX token.
* **Utilities Revenue**: The T-REX ecosystem includes various solutions essential for projects utilizing the protocol. Revenue is generated from the usage of these utilities, such as Token Deployment, OnchainID, AssetID, add-on smart contracts for subscriptions, redemptions, capital calls, compliance modules, etc. 
* **Liquidity Provision**: The DAO will provide liquidity on both decentralized and centralized exchanges, earning revenue as a liquidity provider. This activity supports the ecosystem by ensuring that T-REX tokens are readily available for trading, enhancing market accessibility.

## Token supply

TGE: Q2 2026

Total supply: 1,000,000,000 

| Class            | Quantity | Vesting     |
| ---------------- | -------- | ----------- |
| Contributors[^1] | 40%      | 1-36 months |
| Ecosystem[^2]    | 40%      | None        |
| Liquidity        | 20%      | None        |

[^1]: ERC3643 Core Contributors: 20%

    10Y Budget for ERC3643 Members: 20%

[^2]: Community: 20%

    Builders: 20%


---

# Agent Instructions: 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:

```
GET https://docs.t-rex.network/t-rex-network/t-rex-token/tokenomics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.