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

# RWA Tokenomics

## Overview

Each IP asset registered and launched on BeatSwap follows a standardized RWA tokenomics model that defines the total supply, token naming conventions, and allocation structure.

All token distributions are designed to reflect the contributions of stakeholders while enabling liquidity and accessibility within the BeatSwap ecosystem.

***

## Token Structure

<table><thead><tr><th width="234">Item</th><th>Description</th></tr></thead><tbody><tr><td>Total Supply per IP Asset</td><td>2,000 tokens</td></tr><tr><td>Token Name</td><td>Same as IP Asset Title (e.g., song name)</td></tr><tr><td>Token Symbol</td><td>Unique symbol generated from the IP Asset Title</td></tr></tbody></table>

***

## Allocation Breakdown

This allocation breakdown illustrates the tokenomics structure for music IP, where roles such as composer, lyricist, and singer are reflected.\
The same framework can be adapted to other categories of IP-Rights (e.g., film, gaming, publishing) with role-specific adjustments to ensure fair distribution among verified contributors.

{% @mermaid/diagram content="pie

```
"BeatSwap" : 12
"Composer" : 6
"Lyricist" : 6
"Singer" : 8
"Launcher" : 50
"Liquidity" : 18
```

" %}

<table><thead><tr><th width="359">Recipient</th><th width="99">Allocation</th><th>Notes</th></tr></thead><tbody><tr><td>BeatSwap (Copyright, Non-circulating)</td><td>12%</td><td>Held for exclusive rights management; not traded</td></tr><tr><td>Composer (Neighboring Rights)</td><td>6%</td><td>Tradable on BeatSwap</td></tr><tr><td>Lyricist (Neighboring Rights)</td><td>6%</td><td>Tradable on BeatSwap</td></tr><tr><td>Singer (Neighboring Rights)</td><td>8%</td><td>Tradable on BeatSwap</td></tr><tr><td>RWA Launcher Initial Offering<br>(Neighboring Rights)</td><td>50%</td><td>Sold to early participants via Launchpad</td></tr><tr><td>Initial DEX Liquidity (Neighboring Rights)</td><td>18%</td><td>Supplied as initial liquidity on BeatSwap</td></tr></tbody></table>

***

## Key Points

* **BeatSwap** retains 12% of the token supply as **the copyright portion for rights control**; this allocation represents the underlying copyright itself, is **non-circulating**, and will **never be sold**.
* **Neighboring Rights** shares are allocated to Rights Holders (e.g., composer, lyricist, singer for music; director, writer, actor for film), and these are **freely tradable** after Launchpad.
* **50% of the total supply** is offered to early participants during the **RWA Launcher Initial Sale**.
* **18% of the total supply** is reserved for **initial liquidity pools** on BeatSwap to support secondary market trading.
* All token holders, including fans and liquidity providers, are eligible to **earn royalties** based on PoR staking and verified usage activity.

***


---

# 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://beatswap.gitbook.io/beatswap/tokenomics/rwa-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.