Mintnite
Can I add multiple files in one NFT?
Last Updated: July 31, 2023No, you can’t. You cannot add more than one file in one NFT under the public or private category. If you need to do so, you need to upload multiple files and duplicate the same wallet address on a list when minting as shown below. This will create multiple unique NFTs with different token IDs and all are assigned to the same wallet. 0x8d0CE07483596c76e0C8bB17Eb32e7dA7e3d270c 0x8d0CE07483596c76e0C8bB17Eb32e7dA7e3d270c 0x8d0CE07483596c76e0C8bB17Eb32e7dA7e3d270c 0x8d0CE07483596c76e0C8bB17Eb32e7dA7e3d270c 0x8d0CE07483596c76e0C8bB17Eb32e7dA7e3d270c
What’s the difference between public and private category?
Last Updated: July 31, 2023Public category is for creating NFTs or SBTs containing files that are visible publicly on the blockchain. Private category only stores the file hash string (such as 4669105d5a7440f09650d63986ccc1161efab6a252a1e5e5ddbb425410252564) in the NFT. Typically, you’d always use the public category. You would only use the private category when you need to notarize a personal file that you do not which the public to access. Thus, the file hash acts as proof of your file’s existence by carrying its hash string on the blockchain.
Can I mint more than one NFT at once?
Last Updated: July 31, 2023Yes, certainly. You can mint many ERC721 NFTs or SBTs for many wallets under one blockchain transaction. You need to provide the same amount of files and wallet addresses. Each file will be stored in one NFT with a unique token ID for each wallet. The files are stored on IPFS decentralized data storage network. The order shall be the first file selected and uploaded will be saved in the first NFT for the first wallet on the list. For example, if you selected file1.png to be the first to be uploaded and the wallet 0x8d0CE07483596c76e0C8bB17Eb32e7dA7e3d270c is the first on your list of addresses, then this wallet will own the NFT containing the file fiel1.png and the token ID shall be 0. Do note that you can’t create multiple NFTs for one single wallet at once. This applies to public and private NFTs.
I’m getting rate limit error when uploading my NFT files
Last Updated: July 31, 2023Because we use nft.storage to store your NFT files on IPFS, there’s a limit on how many files you can upload at once. Currently, the rate limit will be triggered if the nft.storage API receives more than 30 requests using the same API key within a 10-second window. What you can do is reduce the number of NFTs you wish to mint at once which in effect will reduce the number of files being uploaded to nft.storage at once.
How to view my file hash on blockchain after minting?
Last Updated: August 1, 2023You can view your file hash string by checking the token URI of your NFT under your manage ERC721 token page. Please see below.
How do I get the token ID of NFT after minting?
Last Updated: July 31, 2023The token IDs are displayed under your manage ERC721 token page. You also get to view which wallet owns which token ID via the buttons on the right as depicted below in red boxes.
Is the file hash stored on IPFS or the block itself?
Last Updated: August 1, 2023The file hash string is stored in the block itself on the blockchain, not on IPFS. You may view the file hash by accessing your token on the ERC721 token management page and clicking on the “check token URI” button.
How do I mint an ERC721 soulbound token (SBT)
Last Updated: August 1, 2023To mint a single ERC721 soulbound token (SBT), you may follow this video tutorial below.
How to mint one ERC721 NFT for multiple wallets?
Last Updated: August 1, 2023The video tutorial below demonstrates how you can create NFTs that have similar content for multiple wallet addresses. Each NFT still uses a unique token ID and is owned by an individual wallet. Although the video uses soulbound tokens, the steps are all similar for NFT except that you need to pick an ERC721 NFT smart contract when deploying instead of an SBT contract.
How to mint multiple unique NFTs for different wallets?
Last Updated: August 1, 2023To bulk mint multiple NFTs for different wallet addresses where each NFT contains unique content, please follow the video tutorial below.
Different types of smart contracts on Mintnite
Last Updated: August 8, 2023We offer the following types of smart contracts for you to deploy on Ethereum or EVM blockchain without needing to write a single line of code. Our contracts are based on OpenZeppelin templates and the source code is available on our GitHub channel. ERC20 Contract This is the standard cryptocurrency contract that you may use to mint the widely-accepted ERC20 tokens. Examples of crypto that use this contract standard are USDT, MATIC, USDC and WETH. The tokens created by this contract are fungible and the contract supports 18 decimal places – the recommended standard. This means your contract shall display token balance such as 0.123456789012345678. ERC721 NFT Contract This is the typical NFT contract that is compliant with OpenSea, Rarible and other NFT marketplaces. It mints conventional NFTs and each token payload is stored on IPFS (InterPlanetary File System) which is a decentralized data storage system. The link (e.g., https://ipfs.io/ipfs/bay…/metadata.json) to the payload on IPFS is stored as the token URI. You can add virtually any digital file as the payload as long that they are supported by IPFS. ERC721 SBT Contract SBT stands for soulbound token and it is a hybrid of NFT. Its purpose is to create tokens that are not transferrable by the token holder. Imagine that you wish to issue an NFT certificate to someone, you’d want to use SBT smart contract because you’d want to prevent the token holder from transferring that certificate to someone else. This type of contract is also useful when you wish to issue non-transferrable digital coupons or any NFTs that are meant to identify the person owning the token. It could be used in self-sovereign identity use cases. ERC1155 Contract ERC1155 smart contract is like a cross between ERC20 and ERC721 contracts. It is mainly used in Web3 games where it enables a game developer to mint fungible and non-fungible tokens under one single contract. Each token has a unique ID and a token URI, regardless if it’s fungible or non-fungible. The token URI is used to provide more info about the specific token ID. For example, you’d use ERC1155 if you want to create a fungible type of token called “bananas” which is your in-game currency, and you also wish to issue tradable game items such as hats and masks – the non-fungible items. However, you may also use ERC1155 for other real-world use cases. ERC721 NFT With Access Control This type of ERC721 is more advanced since it offers more control for the contract owner. The creator may issue tokens for any wallets and also burn the tokens even though the tokens were already sent to the wallets. We envisage an array of uses cases where token creators require this feature such as in NFT coupons (used coupons), NFT tickets (for canceled or refunded tickets), NFT certificate (revoking a certificate) and just simply reversing a token issuance due to some error or typos. Contract owners also have the power to assign privileges to other wallets such as the ability to issue and burn tokens. We imagine a scenario where a general manager delegating the token minting and burning tasks to lower-level managers. ERC721 SBT With Access Control This contract is exactly the same as ERC721 NFT, with the exception that the soulbound tokens (SBTs) holders are not able to transfer their tokens out from their wallet addresses. This means the contract owner can mint and issue SBTs to any wallets without them retransferring.
List of mainnets and testnets we support
Last Updated: August 5, 2023Here is the detailed list of blockchains we support. We currently support Ethereum and dozens other EVM chains.
