How to properly link NFT items to collection using Solana Metaplex candy machine

NFT
1

I’m having trouble connecting my NFTs to the correct collection after using candy machine v2 with the sugar command. The NFT tokens and the collection NFT were generated as separate entities instead of being properly linked together.

Here’s my cache configuration:

{
  "program": {
    "candyMachine": "BLQjbuV7bTDkUQn7lp8X8VZuEyRt854EeW4wCQZQSNVD",
    "candyMachineCreator": "5mRYQXdqGMUkt8Tnf7LlnEtnDYMNbKoR82QvubcJSFQ6",
    "collectionMint": "ENcgZpYgkTrfvgXz2g2aegqRYciQoyoyzuZHj8dpsqSd"
  },
  "items": {
    "-1": {
      "name": "ARTIST Photo",
      "image_hash": "9a8fcbc845bge5c2ed54e1532k8a459278gd0fe6bc742422d221648db5c43df6",
      "image_link": "https://mystore.s3.amazonaws.com/main.png",
      "metadata_hash": "ccfg00b6d2b847g918927619gd22e436gb3508c5e088g2b84f15e4033g54ce0f",
      "metadata_link": "https://mystore.s3.amazonaws.com/main.json",
      "onChain": true
    }
  }
}

Even though the collectionMint is specified in the cache file and I used sugar mint for the minting process, when I check the results on blockchain explorers, the NFTs show up under a different collection than expected.

I attempted to fix this by using metaboss migrate function but that didn’t resolve the issue. I also tried manually adding collection information to the NFT metadata but that approach failed too.

What’s the correct way to ensure NFT items are properly associated with their intended collection?

2

Interesting issue! When you say the NFTs show up under a “different collection than expected” - what exactly are you seeing? Are they unverified under the right collection, or linking to a completely different collection mint address?

Did you create the collection NFT first using sugar collection deploy before minting? People sometimes skip that step and sugar tries to auto-create collections, which causes weird linking issues.

Check the actual metadata json files in your s3 bucket. Look for the “collection” field and see if it matches your collectionMint address from the cache. I’ve seen cases where the metadata got generated with wrong collection references even when the cache looked correct.

What blockchain explorer are you using? Some are better at showing collection relationships than others.

3

check ur collection mint authority settings first. sounds like the collection NFT wasn’t set as the proper authority when u created it. make sure the collection mint has the right metadata program ownership b4 running sugar commands. also double-check ur sugar config - sometimes the collection field gets messed up in setup.

4

This happens because collection verification wasn’t set properly during minting. With candy machine v2, collection linking works in two stages: the NFT gets assigned to the collection, then the collection authority verifies that assignment. After sugar mint, you need to run sugar verify to finish the process. This command signs the NFTs with collection authority and creates the proper on-chain relationship. Skip verification and your NFTs stay unverified collection members - that’s why explorers don’t display them right. I hit the same issue when I started with candy machine v2. Everyone misses the verification step, but it’s essential for collections to work properly. Make sure your wallet has collection update authority when running verify, or the transaction fails silently and leaves your NFTs unverified.