Token Management

Smart Contract and Token metadata (JSON objects) can be hosted in various ways for your NFT Collection. Options include:
  • Hosted
    • Using HyperMint to host your Metadata
  • Self Hosted


HyperMint uses AWS infrastructure provided solutions to manage your token metadata securely, globally, and at scale. If choosing to host token metadata with HyperMint, then you can proceed to finish creating your contract and then head to 'Tokens' tab to create your tokens.

Self Hosted

If you decide to self host token metadata, HyperMint requires that token metadata be hosted using a single root url where the token id is added or injected based on the contract type. For information about the required properties, click here.

Using your Own Server

Although HyperMint offers a hosted solution for metadata, it is not required. Any endpoint which can return a JSON object and images can be used.
For information about how metadata should be structured, please refer to this guide on OpenSea:​
If you chose the 'Self Hosted' option, please note that the url structure differs based on the contract type being used. Refer to the below for the distinctions.

For ERC721 Token Metadata

The url must end with the token id. For example: where 1 is the token id.
A working example of a ERC721 metadata file can be found here:​

For ERC1155 Token Metadata

The url must contain the {id}. For example:{id} where {id} is actual token ID in hexadecimal form.
For more information, please reference the ERC-1155 metadata standard.

Using an External Web3 NFT Storage Solution

Immutable Storage

This type of storage is considered "more crypto" than other forms of metadata storage for the simple fact that once the metadata has been uploaded, it cannot be changed.
Various solutions exist including IPFS ( which use peer-to-peer networking to distribute copies of the metadata and maintain their integrity.
To comply with HyperMint, metadata files must be stored in a directory with the convention of the file name being the token id as per the above contract types.

ERC721 Token Metadata on IPFS

The url must end with the token id. For example:
ipfs://QmPtGwEGvVnq1wE9Drt3hQV6msAfRGtptvAMLiYQ7ZPLZE/1 where 1 is the token id.

ERC1155 Token Metadata on IPFS

The url must contain {id}. For example:
ipfs://QmX3wqfVFkdBEc1rFLcRwjn6eixR8D5rBVjvnGttDiMbyh/{id} where {id} is actual token ID in hexadecimal form.
After determining where you will host your NFT Metadata, you can now complete creating your contract and proceed to filling out remaining details in your contract to launch your collection!
For more information on what NFT Metadata entails, see Metadata Basics​


Something not quite right, unclear or can't find what you are looking for? Please let us know at [email protected] and we will get back to you as soon as we can.