# Token Allocation

The $RSNA token is designed with a fixed supply to ensure scarcity while maintaining deep liquidity for the Resona ecosystem. The total supply is capped at 1,000,000,000 $RSNA.

| **Category**              | **Allocation** | **Purpose**                                                                |
| ------------------------- | -------------- | -------------------------------------------------------------------------- |
| **Liquidity & Ecosystem** | **85%**        | Market making (DEX/CEX), community grants, and cultural marketing.         |
| **Incentive Engine**      | **3%**         | Rewards for IP Miners, early curators, and high-resonance creators.        |
| **DAO Treasury**          | **10%**        | Reserved for strategic R\&D, physical RWA audits, and future partnerships. |
| **Team & Advisors**       | **2%**         | Core contributors and technical advisors (1-year cliff, 3-year vesting).   |

**The Vesting Philosophy**

To align interests with long-term holders, the **Team & Advisor** allocation is locked behind a rigorous **1-year cliff**, followed by a **3-year linear monthly vest**. This ensures that the architects of the protocol remain focused on the multi-year expansion of the Resona network.

**Incentive Engine: IP Mining**

Unlike traditional "mining," Resona rewards **IP Miners**—users who bring high-value, verified RWA assets to the chain or curate them during the early discovery phase. $RSNA is distributed based on the "Resonance Score" of the assets they support.


---

# 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.rsnatoken.xyz/4.-tokenomics/token-allocation.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.