> For the complete documentation index, see [llms.txt](https://xrdegen.gitbook.io/xrdegen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xrdegen.gitbook.io/xrdegen/launch-your-collection/launch-your-collection.md).

# Launch Your Collection

***Ready for launch?*** \
\
Here’s how to launch your collection, step by step, through the CREATOR DASHBOARD:

* [ ] Click **"CREATE A COLLECTION"**

* [ ] Fill out the required project details—name, visuals, the works. Details below\....
  1. **COLLECTION NAME** - This one is self-explanatory<br>
  2. **URI** - Do NOT confuse this with URL! \
     This is where you type what you would like to use in addition to your collection's resource ID to direct users to your project\
     FOR EXAMPLE: If you wanted your community to find you at **XRDEGEN.com/collections/MyNFTs**, you would enter **MyNFTs** into the URI field\
     \&#xNAN;*PUTTING IN AN ENTIRE URL WILL CAUSE AN ERROR!*<br>
  3. **COLLECTION DESCRIPTION** - 5,000 character max though short and sweet is always a better look<br>
  4. **FALLBACK IMAGE -** This is the ipfs address for an image that will be used as  the placeholder for your NFT while the metadata updates. To be honest, your community may not even see it, so don't overthink it. You can simply use your collection pfp if you like.<br>
  5. **TAGS -** Hit the ENTER key after each tag you wish to add to your collection on chain. You can add whatever you want!<br>
  6. **CATEGORY -** You can only pick ONE category for your collection from the drop-down list<br>
  7. **SOCIALS -** Please be sure to type the WHOLE URL for each! For example, a telegram link should be entered as \_<https://t.me/\\_\\_\\_\\_\\_\\_\\_\\_\\_\\>\_\_<br>
  8. **MINT PRICE -** Enter your price per mint here! One XRD will be added to the final price to pay for the transaction that reveals your artwork. For example, if you enter 4999 XRD, users that mint your collection will pay 5000 per NFT.<br>
  9. **ROYALTY PERCENTAGE -** This is the percentage you'll receive of each secondary sale of your NFTs. 10% is the max we allow. You CAN update this amount in the future.<br>
  10. **COLLECTION SIZE -** How many NFTs are in your collection?  For an open edition ( a mint with no max supply and repeat artwork/metadata) enter 0<br>
  11. **MINT END DATE - I**f you don't have an end date in mind, set it way out or leave this blank. You can end your mint at any time from the Creator Dashboard<br>
  12. **CLICK DEPLOY NFT -** This locks in the details and adds the collection to your dashboard (does NOT launch the mint yet).\ <br>

* [ ] **LAUNCH YOUR COLLECTION**
  * In the Creator Dashboard, select your new collection from the **DEPLOYED** tab
  * Update any info that you entered earlier, if needed
  * UPLOAD YOUR COLLECTION METADATA WITH A .CSV FILE
    * **Go to** [Format Your CSV File](/xrdegen/launch-your-collection/launch-your-collection/format-your-csv-file.md) **to ensure you are using the proper template**
    * If your CSV is wrong, your collection will not mint properly
  * Setup Mint Phases (optional)
    * To add phases (e.g., whitelist or tiered pricing):
      * Click **Add a Phase**.
      * Set phase name, price, supply cap, mint limit per wallet, start/end dates.
      * Choose **Allow Public** (public phase) or leave unchecked (whitelist-only).
        * If you choose whitelist, you will upload a list of wallet addresses on the next step
      * Add multiple phases as needed.
      * Click **Save Phases**
  * **PREPARE FOR TAKEOFF**
    * Click LAUNCH in the top right corner to finalize your mint info and launch your collection!
      * Your mint will start and end according to the dates you set in the MINT PHASE section

* [ ] **SET-UP WHITELIST, AIRDROPS, AND STAKING (OPTIONAL)**
  * WHITELIST
    * Upload Whitelist CSV for each WL mint phase
      * Wallets on the CSV will receive a whitelist token that must be burned to mint during it's respective mint phase
  * AIRDROPS
    * Upload an Airdrop CSV for each mint phase, if needed
      * The CSV must contain addresses of airdrop recipients and the quantity of NFTs each address is to receive
        * A mint fee (usually deducted from the mint price) will have to be paid for each airdropped NFT
  * STAKING
    * If you wish to allow your holders to stake their NFTs for daily rewards, check the box next to ENABLE NFT STAKING
    * You will have to now choose the following:
      * What token your holders will receive (You can create a token right here on XRDegen if needed)
        * In order to choose a token, it must be in your wallet already
      * The start date for staking
      * Token reward per day
        * This is the TOTAL amount of tokens per day that will be divided between staked NFTs
      * Starting Reward Amount
        * This is the amount of tokens you will be depositing into the staking contract today.
        * These tokens will be locked in the staking contract. If they run out before you deposit more, staking rewards will stop
        * There is a one-time fee to set up staking for your community

### Congratulations! Your collection is now fully set-up!

#### If you have questions, please open a support ticket in our discord. You can find the link in [Contact & Community](/xrdegen/contact-and-community.md)


---

# 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://xrdegen.gitbook.io/xrdegen/launch-your-collection/launch-your-collection.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.