🚀
HeyMint Launchpad
  • Welcome to HeyMint Launchpad!
  • Introduction
    • Setting up your collection
    • ERC-721(A) vs ERC-1155
    • FAQ
      • What to do when the deployment wallet was hacked?
    • Deploy Proxy Contract
    • Manage Access
  • Pricing
    • How the HeyMint Fee works
    • Basic Plan
    • Plus Plan
    • Premium Plan
  • Create a ERC-721A Collection
    • Set up smart contract
    • Art & Metadata
      • Create layer files
      • Generate art
      • Set Token Name
      • Set up pre-reveal image
      • Generate metadata
      • (Advanced) Upload art & metadata
      • (Advanced) Set token URI
      • Upload & Pin to IPFS using Pinata
    • Manage smart contract
      • Before deployment
        • Affiliate Minting
          • Affiliate Earnings
        • Enforced Royalties
        • (Presale only) Set up allowlist
        • Advanced features
          • Free Claim
          • Burn to Mint Feature
            • Creating a Burn to Mint Collection
            • Map URI to first burn token ID
        • Deployment (Testnet)
        • How to get ETH on Testnet
        • What to test on Testnet
        • Deployment (Mainnet)
      • After deployment
        • Verify contract
        • Start/stop public sale/presale
          • Allowlist Checker
        • Set up mint website
          • Use HeyMint mint page
            • Warpcast Integration for Mints
          • Use mint button embed
            • Website builder incompatibility
        • Set up credit card payment
          • Mint Using a Credit Card
        • Reveal art
        • Withdraw your funds
        • Enable Burn to Mint
          • Set up burn to mint page
          • Start/stop burn to mint feature
    • Create a ERC-721A collection using generated Art
      • Tokens (Beta)
  • Create a ERC-1155 collection
    • Set up smart contract
    • Upload assets to IPFS
    • Manage smart contract
      • Before deployment
        • (Presale only) Set up allowlist
        • Deployment (Testnet)
        • What to test on Testnet
        • Deployment (Mainnet)
      • After deployment
        • Verify contract
        • Start/stop presale/public sale
        • Set up mint website
        • Withdraw your funds
  • After creating a collection
    • Set up a collection in marketplaces
      • Minting an NFT
      • Airdropping/gifting an NFT
  • HeyMint Buttons
  • Migrate
    • HeyMint Launchpad Closure Announcement, FAQs, and Migration Guide
      • ERC-1155 Migration Guide
Powered by GitBook
On this page

Was this helpful?

  1. Create a ERC-721A Collection
  2. Art & Metadata

(Advanced) Set token URI

Previous(Advanced) Upload art & metadataNextUpload & Pin to IPFS using Pinata

Last updated 10 months ago

Was this helpful?

Making your custom metadata causes most of the issues when using Launchpad due to incorrect metadata setup. If you are using this feature, we highly recommend to read to make sure your metadata is set up correctly.

Go to Upload layers section and click "I already have my art" at the bottom.

Next, select "Yes, both"

Once you select the options above, you will see the input for Token Base URI. Set the IPFS link that you saved metadata folder and hit "Validate & Save".

As custom metadata tends to have issues, we try validating your metadata by simply checking if the IPFS link you provide contain correctly formatted metadata.

Error: Metadata files should not have extensions

Error: Metadata files not found

If you see this error message, there is a high chance your metadata files are saved incorrectly. Please make sure:

  • Your token base URI is pointing a folder that contain metadata files (JSON format), not the folder of your asset files

If you are sure metadata is set up correctly, you can move forward as your token base URI is saved even if it's not correctly validated.

Once you are able to save your token base URI, you are all set!

If you see the following messages, your metadata files have .json file extensions which doesn't work with our Launchpad. Reformat your metadata files to be just a number with no file extension (for instance, 1,2,3 not 1.json, 2.json, 3.json - you can see the example from ).

Your metadata has image_url and image_url points to the right location that you store your image (example ). Please note that even if you set animation_url (mp3, mp4 files etc.), you will still need to set an image_url

here
here
How to create Metadata blog post