Hey everyone! I need some guidance with my Solana NFT project.
I created a collection using candy machine v2 and stored the metadata on arweave. The problem is that only 50% of the planned tokens got minted, which created issues with the naming system. Some NFT holders now have tokens with names that go beyond what should be the maximum 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 clear instructions on how to do this properly.
Has anyone dealt with something similar? What’s the best approach to migrate metadata from arweave to AWS while updating the collection info? Any step-by-step advice would be awesome!
Interesting situation! I’ve got a few questions - when you say the naming got messed up because only 50% minted, do you mean the actual token names in metadata or just the numbering? Like did you end up with tokens named “MyNFT #2000” when your max supply should’ve been 1000?
What new features need AWS control? You might be able to keep some stuff on Arweave for immutability and use AWS just for the dynamic parts.
Have you checked if your update authority is still valid? With candy machine v2 setups, the authority sometimes gets transferred or burned without people realizing it until they try to make changes.
When you migrate to AWS, are you keeping the same metadata structure or redesigning it? And how will this affect marketplace compatibility? Some platforms get weird when metadata URLs change suddenly.
What’s your timeline? Do your holders know this is happening?
Migrating your NFT collection’s metadata from Arweave to AWS is certainly achievable. Begin by utilizing the Metaplex Token Metadata program to update the URI field for each token to the new AWS location. First, ensure your metadata files are correctly uploaded to S3 with the necessary CORS configuration in place. It’s essential to have the correct update authority over your collection. I recommend scripting the updates using @solana/web3.js and @metaplex-foundation/mpl-token-metadata for an efficient batch process. Be wary of potential downtime with AWS; I encountered issues with S3 that halted metadata retrieval, making the transition quite challenging. Also, consider the transaction fees you’ll incur as each token update is treated as a separate transaction. Overall, the process took me about a week for 2,000 tokens, including testing.