> For the complete documentation index, see [llms.txt](https://docs.relicsprotocol.com/relics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.relicsprotocol.com/relics/further-features/syndicates-collections.md). # Syndicates - Collections {% hint style="info" %} **Disclaimer:** [here](/relics/introduction/disclaimer.md) {% endhint %} {% hint style="info" %} This document only describes our current implementation/idea about the feature. {% endhint %} [Chests](/relics/further-features/chests-nfts.md) are part of a Syndicate, comparable to an NFT collection. Syndicates can be deployed permissionlessly. Each syndicate has the following properties, set by the protocol message: * Relic (which relic the collection belongs to) * Unit (amount of relics per chest) * Supply * Inscription (must be spent on creation) * Royalties (charged in $MBTC on creation and destruction of chests) * Lock configuration * Reward configuration There can be multiple syndicates per relic, with no restriction on who can create them. This allows creators to deploy multiple syndicates for their relics, communities to launch NFTs for their relics, or to enable parts of communities to compete against each other. It is easy to imagine that a relic could become the base commodity for a community that creates numerous collections, driving innovation in art, tokenomics, and the social aspects of community-driven collections. ### Royalties The protocol incorporates a royalty fee system. The royalty system allows creators to earn a predetermined percentage from chesting and unchesting. These royalties go to the owner of the syndicate inscription. ### Staking Pools Syndicates can be used to configure staking pools. Creators of a relic will have the option to automatically distribute relics to chests of pre-determined syndicates. Those rewards can be claimed by unwrapping. --- # 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.relicsprotocol.com/relics/further-features/syndicates-collections.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.