> For the complete documentation index, see [llms.txt](https://whitepaper.sonorus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.sonorus.network/music-mint-mechanism/publishing-revenue-distribution.md).

# Publishing Revenue Distribution

To maintain a sustainable token system, **80% of the $RUS tokens used to issue new copies of Music Record NFT(s) are permanently burnt.** The rest of the $RUS tokens paid to issue new copies are considered as publishing revenue for each piece of music. Then Sonorus Protocol automatically distributes the rest of the funds to music nominator(s) and the protocol's revenue pool according to the following mechanism.

#### Music Nominator Rewards

Every time a new Music Record NFT is issued, a fixed portion of the issue price will be credited as rewards to the user who nominates the song to Sonorus. Currently music nominator rewards proportion is set at **5%** of the issuing prices.

###

###

####


---

# 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://whitepaper.sonorus.network/music-mint-mechanism/publishing-revenue-distribution.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.