HeyMint Launchpad Closure Announcement, FAQs, and Migration Guide

Important Announcement

After a lot of thought, the HeyMint team has made the tough decision to sunset the HeyMint platform, including Launchpad, Quests, and all related services as it’s no longer sustainable for us to continue operating in the current market environment. We’ll be officially signing off all services on May 31, 2025.

This means that hosting for collections and metadata pinned via our IPFS will also come to an end and eventually become unavailable. To help make this transition as smooth as possible, we’ve put together a migration guide to support you and avoid any disruptions to the collections you’ve trusted us with.

Here are the key dates to keep in mind:

• May 31, 2025 – Art and collection generation services will close, and new user sign-ups will be disabled.

Frequently Asked Questions (FAQs):

Launchpad Migration Guide

For ERC-721A – You can follow the full steps outlined below on this page.

For ERC-1155 – Due to the structure of ERC-1155 collections, please continue to the ERC-1155 Migration Guide for specific instructions.

Thank you for trusting us with your NFT collection and for being part of our journey in Web3. While it’s tough to say goodbye, we want to make sure you can continue managing and staying connected with your project even after HeyMint shuts down.

To start migrating your collection, please head over to launchpad.heymint.xyz and follow the steps to export your assets and move them to a new IPFS host.

Please note: depending on the size of your files and metadata, there may be additional costs when uploading to a different IPFS provider.

Step 1. Choose the collection you wish to migrate

From your Launchpad dashboard, select the project or collection you'd like to begin migrating.

Keep in mind: migration only applies to projects that have been deployed to the blockchain (mainnet or testnet) and are currently using HeyMint’s IPFS hosting for their images and metadata.

If your project is already using your own IPFS host, there’s no need to take action - your assets won’t be affected by the shutdown.

Step 2. Access the Export Collection feature

In your Launchpad dashboard, head to the left-hand sidebar and click on Export Collection. This option will only be visible if your project has been deployed to the blockchain.

When starting the export, please keep the browser tab open to avoid any interruptions while your files are downloading and updating.

Step 3. Download your collection’s artwork / images.

Start by selecting the first action: Download collection images. Follow the on-screen prompt and choose a folder on your computer where the images will be saved. Once the download is complete, double-check your local folder to make sure everything came through.

Step 4. Upload your collection’s artwork / images to your chosen IPFS host

After confirming that your images have been successfully downloaded, go ahead and upload them to the IPFS host of your choice - such as Storacha, Pinata, or Web3.Storage.

Storacha Upload Guide

Here’s how to proceed on Storacha:

1. After registering and creating your space, upload the folder that contains your downloaded assets.

   • For 721A projects using art-gen, you'll be prompted to select the folder where the files were saved.

   • For 721A (Token Flow) and 1155 projects, your download will come as a ZIP file. Be sure to unzip it before uploading to your IPFS host.

2. Once the upload is complete, copy the CID provided. The CID is a unique string (usually starting with bafyxxxxxx) that serves as a digital fingerprint for your uploaded content. It allows anyone to locate and access your files through IPFS gateways.

You can use gateways like ipfs.io or w3s.link to view your uploaded assets using the CID, as shown in the examples below.

Your chosen IPFS host will usually display the CID of your uploaded folder or repository in its dashboard—just like the example below from Storacha.

To help guide you through this step, we've included a video below showing the process on a Windows setup using a sample 721A art-generated project.

In this video, you'll see how to:

1. Download your images and assets

2. Upload them to a new IPFS host (e.g. Storacha)

3. Copy and save the newly generated CID

Pinata Upload Guide

Logging into Pinata

1. Go to Pinata and create an account: https://app.pinata.cloud/

Uploading art or metadata files & getting CID

Note: Art & metadata files should be uploaded separately using these steps.

1. Click the '+ Add' button, then select 'Folder Upload'.

   
2. Enter the name, then click 'Upload'.

   
3. Once it finishes the upload, a new CID will be displayed next to the name. Copy the CID for pasting into Launchpad:

Step 5. Update your new image CID

After uploading your images to your chosen IPFS host, copy the CID (Content Identifier) and paste it into the “CID for image files” input box in your Launchpad dashboard. It should look something like this: bafyxxxxxxx (with the "x" being random characters). Once entered, click Save image CID.

Step 6. Process and update your collection’s metadata with the new image CID

Next, go to “Process and download the updated metadata with new image URI” and click “Update Metadata.”

This step may take a little time - it will gather your collection’s existing metadata and replace the old image links with the new CID you just saved. Once the process is complete, download the updated metadata as a ZIP file.

If you'd like to double-check that the image and animation URLs in the metadata have been updated correctly, you can drag any of the metadata files into your browser to view its contents. See the example below for a comparison.

In the original metadata, you’ll see a different CID in the image field: bafybeibxq6bezazq2iwdhk5p23fwsllbz6372kvulabouxmsuwv35k2gbm

In the updated metadata generated by the migration tool, you'll see that it now uses the CID you saved earlier: bafybeihwusrv4unp3mxdncfhg6rikbtasjprcy4kndhniwnldjofnkhyba

Step 7. Upload the updated metadata files to your chosen IPFS host

Once you’ve confirmed the updated metadata files are complete, head over to your chosen IPFS provider and upload all the files together in one folder. This will generate a new CID for your metadata, which you'll copy and use in the final step.

We've included a video walkthrough below that covers this step (along with Step 6), shown using a Windows setup. The process is the same for both 721A and 1155 projects, so you can follow along regardless of your collection type.

In this example, the CID provided after uploading the updated metadata is: bafybeihzx37ul3oucta45yb2paxqesloa66lccs6liamydsi45hw5feqlm

You can view the contents of this CID here: https://bafybeihzx37ul3oucta45yb2paxqesloa66lccs6liamydsi45hw5feqlm.ipfs.w3s.link/

Step 8. Update your collection’s metadata on-chain

Now that you have your new metadata CID, head back to your dashboard and input the updated IPFS URI. The format should be:

ipfs://<your CID here>/

For this example, it would be:

ipfs://ipfs:bafybeihzx37ul3oucta45yb2paxqesloa66lccs6liamydsi45hw5feqlm/

Click Validate & Save, and once everything checks out, you’ll be prompted to sign a transaction through MetaMask. This will update your collection’s metadata on the blockchain.

You can refer to the video below to see how the update process works and how to confirm that the metadata has been successfully changed.

Here are the details of the test collection used in the recording:

1. OpenSea (Testnet) collection link: https://testnets.opensea.io/collection/yababoo

2. Project contract on Sepolia: https://sepolia.etherscan.io/address/0xb90938d30c0f450e9b35bfc66e1e2c8374767bbc

You can also confirm if the update was successful by checking your project through a blockchain explorer.

In our example, the project is deployed on Sepolia (Ethereum), so we'll use sepolia.etherscan.io as the explorer.

Here’s how to check:

1. In the sidebar, click Smart Contract

2. Under the Overview tab, click the Contract Address. Make sure your contract is marked as Verified

   If it’s not, you’ll need to click Verify Now and complete the verification before continuing

   
3. In the blockchain explorer, click on the Contract tab, then select Read as Proxy.

   Note: This option will only appear if your contract has been verified. If you don’t see it, please go back and complete the verification step first.

1. Scroll through the available methods and look for either:

   • tokenURI – for 721A projects

   • uri – for 1155 projects

   Click on the appropriate method, enter the token ID you want to check (e.g. 1), and click Query. The current metadata URI for that token will appear below.

You can also check out the video below, which walks through the steps above using a 721A project. The process is nearly the same for 1155 projects—the only difference is that you'll use the uri method instead of tokenURI.

Once you've completed all the steps and confirmed that your metadata URI now points to your own IPFS host, your migration is officially complete. You've successfully exported your project's metadata and assets to a location you fully control.

Step 9. Make sure your NFT appears correctly on marketplaces

After you changed the token URI, make sure to go to one of the marketplaces, refresh metadata of one of the NFTs, and make sure it still displays correctly.

You're All Set!

Once you've completed all 9 steps, your collection will be updated and ready to go with its new image and metadata CIDs. Your smart contract remains on-chain and fully functional - HeyMint was just the launchpad, and your project lives on.

If you run into any issues or have questions along the way, feel free to reach out to us at [email protected]. We'll continue to support users until our closure, but please note that response times may be a bit slower than usual as we operate at limited capacity.

Thank you again for being part of HeyMint 💜