> 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/relationship-between-content-tokens-and-protocol-layer-tokens.md).

# Relationship Between Content Tokens & Protocol-Layer Tokens

The “Content Tokens and Co-Creation Economy” chapter mainly introduces Song Token, Club Token and Super IP Token. These are application-layer tokens directly linked to specific content, creators and virtual idols.

This chapter focuses on the protocol-layer token system that supports the entire ecosystem: $MIURO, $SIG and MU.

These two systems do not exist separately. They are closely connected through multiple mechanisms, forming a complete economic closed loop.

### 1. Connection in Value Flow

When users purchase or trade content tokens:

* Trading activity generates fees, part of which enters the protocol-layer burn mechanism or treasury pool.
* When songs linked to content tokens are played or used commercially, Miuro Pay Protocol uses $SIG as the settlement medium for real-time revenue distribution.
* Revenue earned by creators through content token issuance may eventually create demand for $MIURO, such as paying generation fees or upgrading nodes.

### 2. Connection in Incentives and Demand

The activity of content tokens directly increases $SIG usage, because royalty settlement is mainly handled through $SIG.

This triggers more SIG burning and strengthens overall deflationary pressure.

Node operators provide computing power to support content generation and distribution, earning MU / $MIURO rewards in return. This provides creators with the underlying compute infrastructure needed for content production.

After creators issue content tokens, fan participation increases overall network activity, which further strengthens demand for $MIURO governance and long-term value.

### 3. Connection in Governance and Parameters

As the governance token of the protocol, $MIURO allows holders to participate in DAO decisions, including:

* Adjusting content token trading fee rates
* Modifying App Store revenue share ratios
* Optimizing SIG burn rules
* Adjusting Cloud Node synthesis parameters

This means the rules of the content token ecosystem are influenced, to some extent, by $MIURO holders.

### 4. Positioning Within the Triple Flywheel

Within the “triple flywheel”:

* **Content** refers to content creation and content token issuance.
* **Token** includes both content tokens at the application layer and $MIURO / $SIG at the protocol layer.
* **Compute** is supported by the MiuroBox node network as the underlying infrastructure.

Through the connection between content tokens and protocol-layer tokens, these three parts form a complete loop:

Content production → Value distribution → Compute incentives

### Summary

Content tokens give specific works and virtual idols the ability to become tradable and revenue-sharing assets.

Protocol-layer tokens, including $MIURO, $SIG and MU, are responsible for settlement, incentives, governance and value capture across the entire network.

Together, they reinforce and support each other, forming the core economic logic behind MIURO’s vision of “Content Becomes Capital”.


---

# 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/relationship-between-content-tokens-and-protocol-layer-tokens.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.