Deployment Advice: 
KRC-721 NFT Deployment Best Practices

As part of our ongoing commitment to support and grow the Kaspa ecosystem, we at $NACHO have been working tirelessly to test and optimize the deployment of our #KRC721 NFT collection. Through our experience, we’ve uncovered valuable insights that we’re excited to share with the community to help streamline your projects and avoid common pitfalls.

Here’s our advice for structuring your IPFS files and deploying your NFT collections:

---

### IPFS File Structuring

1. Images Folder:
- Create a dedicated folder for all NFT images: This folder should exclusively contain the images for your NFT collection.
- Include file extensions: Each file in the folder must have a proper extension such as .png or .jpg.
- File naming convention: Ensure the files are named sequentially to match the metadata files. 
- For example, if your collection contains 500 NFTs, the folder should have exactly 500 files named 1.png, 2.png, ..., 500.png.

2. Metadata Folder:
- Create a separate folder for metadata files: This folder should contain only metadata files and no other types of content.
- No file extensions: Metadata files should not have extensions like .json, even though their contents should be JSON.
- File naming convention: The folder should contain a metadata file for each NFT, sequentially named to match the corresponding image file (e.g., 1, 2, ..., 500).
- Include one additional metadata file named collection. This file will serve as the collection’s cover and should also have no file extension.
- Metadata "image" field: Ensure that each metadata file includes an "image" field pointing to its respective image using the format ipfs://imagesFolderCID/1.png (replace 1.png with the actual file name).

Example of the “Collection” Metadata File:This Collection Metadata file is particularly important for displaying Collection level content and links onbut not required. 

---

### Deployment in KSPR Bot

When deploying your collection:
- Use only the CID of your metadata folder when prompted by the KSPR Bot.
- Do not include ipfs:// in the input; the bot will parse the raw CID directly.

By adhering to this structure, you can:
- Simplify the deployment process.
- Minimize errors and mismatches between images and metadata.
- Ensure a seamless experience for users interacting with your NFT collection.
- Ensure your collection looks great in both the #KSPR Bot Wallet and #KatScan

---

We’re excited to see the creativity and innovation that the community will bring to the Kaspa blockchain. If you have any questions or would like further assistance, feel free to reach out. Together, we can make deploying KRC-721 collections simple and efficient for everyone!

#NachoNation @NachoWyborski @KsprBot @BlockchainBants @Chris_Hutch7 @WolfysBar @LevendiPro @Cryptopumpzzzz
#NACHO #KRC721