# Dynamic Daily Yield Amount

Building the popularity of music is like building an ideological consensus among audiences. Therefore, Sonorus implements a dynamic yield calculation system to reflect music consensus among Sonorus community. In this system, the amount of $RUS tokens to collect for each copy of Music Records varies based on the Heat Score Ranking of corresponding songs, which is dynamically calculated every day. **Essentially, the higher a song's Heat Score Ranking among all the music in the Sonorus catalog, the greater the $RUS token yields its active NFTs holders will receive on the following day.**

### Heat Score Ranking Details

A song's Heat Score is updated daily at 00:00:00(UTC) to reflect the most recent popularity of the song. The Hear Score is composed of the sum of the following 3 subscores:

1. **Total active copies score**
   1. Each active copy of Record NFT held by any Sonorus user at 00:00:00(UTC) counts 1 point toward the total active record score
2. **Last 7-day newly issued record score**
   1. To reflect more recent popularity of songs, if a song's newly issued copies of Record NFTs in the last 7 days exceed 10 copies, each new copy in the last 7 days counts 5 points
   2. If a song's newly issued copies of Record NFTs in the last 7 days do NOT exceed 10 copies, each day since the song was published counts as -10 points
3. **Boost score**
   1. Any user can boost a song's Heat Score with their $RUS tokens. For every 3 $RUS tokens used to boost will add 1 point towards the total score. Only those $RUS used to boost today will be counted.

In summary, if a song has *x* active copies of Music Record the current day, *y* newly issued copies of Music Record in the past 7 days, and receives *z* boost $RUS the current day, then its Heat Score *H* will be:

* If *y>10*, then *H=x+5y+z/3*
* If *y<=10* and the song has been published for *n* days, then *H=x-10n+z/3*

### **Ranking Rules**

Every day at the end of the day (UTC-0), Sonorus will rank all songs with a score from the highest to the lowest, and calculate the percentile ranking of each song among all ranked songs. The percentile ranking results will eventually determine each song's yield tier.

* For instance, if there are 100 songs with positive total scores, and song A has the highest score, it will rank in the top 1%. If song B is ranked 40th, it will be positioned in the top 40%.
* In cases where multiple songs have the same ranking, the percentile rankings are rounded down. For example, if the top 10 songs among a total of 100 songs with active copies have the same Heat Scores, the yield tier for that day will be calculated based on the Top 10% percentile for all those songs.

### Daily Yield Tiers

| Percentile Ranking | Yield Tier per Active Record |
| ------------------ | ---------------------------- |
| 5%                 | 6 $RUS                       |
| 10%                | 4 $RUS                       |
| 40%                | 2 $RUS                       |
| 70%                | 1.5 $RUS                     |
| 100%               | 1 $RUS                       |


---

# 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:

```
GET https://whitepaper.sonorus.network/daily-record-nft-token-yield/dynamic-daily-yield-amount.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.