Setting Collection Name for NFTs minted with Solana's Candy Machine v2

NFT
1

Hey folks, I’m scratching my head over this Solana NFT issue. I used Candy Machine v2 with sugar to mint some NFTs. Everything seemed fine at first, but now I’ve noticed a problem.

My NFTs and the Collection NFT ended up in separate collections. Weird, right? I’ve got the collection mint address in my cache file, and I used sugar mint as usual. But when I check on explorers like Solscan, the collection is different.

I tried a few things to fix it:

  • Used metaboss to migrate (no luck)
  • Added Collection items to the NFT’s metadata (didn’t work either)

Any ideas on how to get the Collection name set correctly? I’m kinda stuck here.

Here’s a simplified version of my cache file:

{
  "program": {
    "candyMachine": "ABC123...",
    "collectionMint": "XYZ789..."
  },
  "items": {
    "-1": {
      "name": "Cool Camera",
      "image_hash": "123abc...",
      "metadata_link": "https://example.com/metadata.json",
      "onChain": true
    }
  }
}

Any help would be awesome. Thanks!

2

hey ava, i’ve run into smth similar before. have u tried using the metaboss set_collection command? it might do the trick. also, double-check ur config.json file - sometimes the collection details can get messed up there. if nothing works, u might need to remint :confused: good luck!

3

I encountered a similar issue with Candy Machine v2 and collection naming. One solution that worked for me was using the Metaplex CLI tool. It has a ‘set-collection’ command that can update the collection for existing NFTs. You’ll need the collection’s mint address and your NFTs’ mint addresses.

Before trying that, though, verify your config.json file. Ensure the ‘collection’ field is correctly set with the right mint address. If that looks good, try the CLI approach.

If all else fails, you might need to consider burning and re-minting. It’s not ideal, but sometimes it’s the only way to correct collection issues. Just be sure to communicate with your holders if you go that route.

4

hey there ava61! that’s a tricky situation you’ve got there. i’ve seen this happen before with candy machine v2, it can be super frustrating :weary:

have you considered using the metaplex js sdk? it’s got some nifty functions for updating collection info. might be worth a shot if you haven’t tried it yet.

also, curious - did you verify the collection nft was created properly before minting? sometimes that can cause weird issues down the line.

oh, and random thought - have you checked if there are any recent updates to sugar? maybe there’s a patch that addresses this?

keep us posted on how it goes! we’re all rooting for you to figure this out :raised_hands: