Comment on page
The building block of any NFT is the contract that you first need to deploy to a blockchain. Think of this contract as public way to show who owns which NFT (i.e., it's a simple table that has the user’s wallet address in the left column and the NFT the user owns in the right column). Below are the types of contracts available on 3mint.
This standard is used for creating tokens that are all non-fungible. Non-fungible means that an item is one of a kind, completely unique, and can't be traded for another item. Examples of collections that use ERC-721 include Bored Apes Yacht Club, Cryptopunks, and Cryptokitties.
- Non-fungible tokens representing ownership of arbitrary data.
- Only one NFT can reside in a single contract.
- Ideal for digital assets that represent one's immutable ownership of those assets (e.g. digital art).
This standard is used for creating tokens that can be fungible, semi-fungible, and/or non-fungible. This is a common choice for creating multiple copies of a token and minting many NFTs at scale. Example use cases include in-game items and pick-ups, NFT tickets, songs, proof of attendance, etc.
- Semi-fungible tokens categorized by token kind.
- Multiple NFTs can reside in a single contract.
- Ideal for gaming collectables, membership badges, and POAPs.
This standard is used for creating the equivalent of virtual currencies on a blockchain. By default, every ERC-20 token is fungible and is not considered an NFT. There is no artwork or other media (image, video, etc.) attached to the token.
- Fungible token that can be used as currency
- No digital content or metadata associated
- Ideal for loyalty points
It is important to understand your current and future use case before committing to a contract type as the contracts are not upgradable and can't be changed once deployed. If you would like a more technical breakdown of each contract available on 3mint, visit the Contract Architectures page