Choosing the right contract

Before a file can be minted into an NFT, you must deploy and verify a corresponding NFT smart contract on Chiliz Chain. This is a crucial step to ensure transparency and enable interaction with your contract on-chain.

Which smart contract to use?

There are many smart contracts in the blockchain world, and it might not be obvious which one is suitable for NFT minting.

Which smart contract you need depends on what kind of NFT project you have in mind:

  • One unique item: Use an ERC-721 NFT contract, and mint a single item with it.

  • Many unique item: Use an ERC-721 NFT contract, ans mint a collection of items with it.

  • Several copies of the same item: Use an ERC-1155 Multi Token contract (allows one item to have more than one instance).

  • Several copies of several items: Use an ERC-1155 Multi Token contract as well.

There are others smart contracts (known as contract extensions or variants) for different usages (such as ERC-2981 for Royalties, ERC-4906 for Metadata update event, ERC-721 Drop for lazy-minting, etc.), but for now, knowing about ERC-721/1155 is enough.

The most secure and common way to obtain a NFT-minting contract is by using the one from OpenZeppelin, for instance their ERC-721 contract. This saves you from reinventing the wheel and helps prevent common security vulnerabilities.

Deploying and Verifying your NFT Smart Contract

You can deploy your smart contract to Chiliz Chain using reputable platforms, such as Remix IDE or thirdweb, or directly using Hardhat.

Once you have deployed it, you must verify the contract on an block explorer, so that developer tools and platforms can read its ABI (Application Binary Interface) and interact with it.

Follow these guides to deploy then verify your NFT contract:

Deploy and verify a contract

Again, pay attention to use the correct network details for Chiliz Chain and Spicy Testnet:

Connect to Mainnet and Testnet

Last updated

Was this helpful?