Hey everyone! I need some guidance with my Solana NFT project. I created a collection using candy machine v2 and stored everything on arweave. The problem is that only part of my planned supply got minted, which left some token holders with NFTs that have names beyond what should be the actual max supply.
I want to update the collection’s metadata and move everything to AWS so I can have more control over it. This would also help me add new features later on. I’ve been searching for tutorials but haven’t found anything useful yet. Has anyone done something similar before? Any advice would be really helpful!
Wow, this sounds tricky! I’m curious about the technical side - when you say some token holders have NFTs with names beyond max supply, does the metadata show “Item #1001” when your collection caps at 1000?
I haven’t done this exact migration but I’ve been thinking about moving my own stuff from Arweave to other storage. Are you keeping the same token addresses and just updating where the metadata URIs point? You’d probably need the update authority on the NFTs but I’m not sure how complex that gets with a whole collection.
Also - when you move to AWS, are you worried about centralization? Some collectors get concerned when metadata moves off decentralized storage. How are you planning to handle that with your community?
BTW have you looked into Metaplex tooling for bulk updates? Might be worth checking their docs even without good tutorials. Would love to hear how this goes!
I went through this exact thing last year with my collection. First, check if you still have update authority for your NFTs - without it, you’re stuck with the current metadata forever. For bulk migration, I wrote a custom script using Solana web3.js to update metadata URIs in batches. Do small batches (10-20 at a time) or you’ll hit rate limits. You’ll need to call the update_metadata_accounts instruction for each NFT. For AWS hosting, set up proper CORS headers and use CloudFront for better performance. Keep backups of your original metadata files - I had some corrupt during migration and it was a nightmare. The naming issue sounds like your NFTs got minted with sequential names that went past your intended supply? You can fix the names during the metadata update. Just tell your holders about the changes first so they don’t freak out.
you’ll definitely need update authority to change those metadata uris. moving from arweave to aws is doable, but nina’s right - some collectors won’t like ditching decentralized storage. test with a few nfts first before migrating the whole collection. mistakes get expensive fast on solana!