> For the complete documentation index, see [llms.txt](https://potsnftwhitepaper.gitbook.io/pots/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://potsnftwhitepaper.gitbook.io/pots/pots-utility-and-value/sharing-of-royalties.md).

# SHARING OF ROYALTIES

One of the key beneﬁts of owning a POTS NFT collection is the potential to earn royalties from secondary sales. We ﬁrmly believe that this royalty feature will enhance the long-term value of the collection, and we are fully committed to exploring innovative methods to maximize these earnings for our collectors.

A portion of the royalties generated by secondary market sales will be distributed among collectors. We'll provide more details on this exciting development at a later date.

Our approach involves careful consideration to ensure that distributing royalties doesn't impact other utilities like staking and airdrops. Our ultimate aim is to enrich the value of our collection for collectors while safeguarding its long-term worth. As we continue to work on this, we'll keep the community and ecosystem participants updated on our progress, striving to ﬁnd the best solution.


---

# 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://potsnftwhitepaper.gitbook.io/pots/pots-utility-and-value/sharing-of-royalties.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.
