> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/token-economy/usdmiuro-token-allocation-and-design-logic.md).

# $MIURO Token Allocation and Design Logic

### $MIURO Token Allocation and Design Logic

The total supply of $MIURO is fixed at 1 billion tokens, allocated as follows:

| Category                      | Percentage | Amount | Design Purpose                                       | Vesting Cycle     |
| ----------------------------- | ---------: | -----: | ---------------------------------------------------- | ----------------- |
| AI Music Compute Miners       |        20% |   200M | Incentivize long-term operation of hardware nodes    | Geometric halving |
| Ecosystem Incentives          |        15% |   150M | Reward creators, developers and partners             | 48 months         |
| Early Supporters / Financing  |        15% |   150M | Early capital support and shared risk                | 36 months         |
| Team                          |        10% |   100M | Long-term alignment with the core team               | 48 months         |
| Treasury                      |        10% |   100M | Protocol security, governance and emergency reserves | 66 months         |
| AI Music Compute Nodes        |         8% |    80M | Support the Cloud Node ecosystem                     | Geometric halving |
| AI Music Copyright Incentives |         8% |    80M | Long-term incentives for original content production | 96 months         |
| Liquidity                     |         5% |    50M | Initial DEX / CEX liquidity                          | Immediate         |
| AI Music Membership Rewards   |         5% |    50M | Incentivize paid users and the membership system     | 48 months         |
| Community Airdrop             |         3% |    30M | Project cold start and early community building      | 12 months         |
| Advisors                      |         1% |    10M | Strategic resource support                           | 24 months         |

### Allocation Logic

Miners and nodes account for a combined 28%, reflecting MIURO’s emphasis on the DePIN hardware network.

Copyright incentives are allocated a separate 8%, highlighting long-term protection and support for content production.

The team and early supporters are subject to longer lock-up periods, reflecting a long-term commitment to the ecosystem.

### Vesting Mechanism Design

The core purpose of vesting is to prevent large-scale early sell pressure, protecting later participants and the long-term health of the ecosystem.

The team and early supporters are assigned longer cliff periods to prevent insiders from selling too early in the project lifecycle.

Copyright incentives use the longest linear release period of 96 months, reflecting long-term support for continuous content production.

Miner pools and node pools use geometric halving releases, simulating Bitcoin’s scarcity model and encouraging early deployment.


---

# 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.miuro.ai/token-economy/usdmiuro-token-allocation-and-design-logic.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.
