> For the complete documentation index, see [llms.txt](https://docs.cxc.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cxc.world/loot/for-collection-admins.md).

# For Collection Admins

### 🌞 Setting Up Rewards for Collection Owners

To set up NFT staking rewards for your collection, follow these steps:

* Step 1: **Register as a User:** Call `regnewuser` to register yourself on the contract if not already registered.
* Step 2: **Register Your Collection**: Use `setnftcolrew` to register your collection with its reward parameters and time unit settings.
* Step 3: **Add Eligible NFT Templates**: Call `addtemplates` to define which templates in your collection can be staked for rewards.
* Step 4: **Fund the Contract**: Transfer the designated reward tokens to the contract with a `memo` stating your collection name, establishing a `bank` for rewards.
* Step 5: **Optional - Manage Templates**: Adjust eligible templates or remove them as needed with `addtemplates` or `rmtemplates`. Read below for important info.
* Step 6: **Communicate with Your Community**: Inform your community about the staking process, rewards, and any changes to ensure transparency and engagement.


---

# 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.cxc.world/loot/for-collection-admins.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.