> 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/key-nft-elements-of-sonorus-protocol/music-record-nft.md). # Music Record NFT ### What is Music Record NFT? A Music Record NFT in Sonorus is a BEP-1155 token that represents one's on-chain support to a piece of music. Each copy of Music Record NFT, while being placed on active Record Players, grants owners the right to collect daily $RUS token yield as rewards for supporting the song, while increasing the song's total heat score. ### Record NFT Exchange Collectors of Music Record NFTs can freely exchange their Music Record NFTs. Here are 2 ways for collectors to trade copies: * Sonorus In-App Market. Sonorus' App facilitates record trades within the application. Please note that Sonorus will charge 5% of the final sales as transaction fees. * Third-party exchanges. Collectors can withdraw their Music Record NFTs and exchange them on any BSC-supported NFT exchanges. ### Active Copies vs Idle Copies To utilize Record NFTs on Sonorus, Record NFTs must be bound to ACTIVE record players. **Record NFTs bound to active record players are considered Active Copies.** If the record players become inactive, then Record NFTs bound become inactive too. Please note that when Record NFTs are bound to record players, they are not unavailable for trades regardless of the status of the record players. Record NFT owners need to unbind them first before trading. **When Record NFTs are NOT bound to any record players, then they become Idle Copies**. While idle copies are not eligible to receive daily record yield, only idle copies can be traded with other users. --- # 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/key-nft-elements-of-sonorus-protocol/music-record-nft.md?ask=&goal= ``` `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.