🖐️Batch Draft Data
Criteria when creating a batch nft draft (multiple NFT at once)
Batch Draft Requires Uploading a CSV file with the below specified columns. The column requirements will be similar to its corresponding field requirements in single mint. Please name the columns as specified exactly.
In addition, you must also upload image and video files you specified in the csv.
Required Columns
id: The id of the nft.
Must be an integer greater than 0 in text. Must be unique in combination with the contract address.
contractAddress: The contract address used to mint the nft.
Must be a valid contract address from the Marketplace Contracts tab.
Contract address should be either a ERC1155 or ERC721 contract.
Must be a valid contract address in text on the network you specified in the network column.
title: The name of the nft.
Must be text.
description: The description of the nft.
Must be text.
totalSupply: The total supply of the nft.
No limitation on the value it self but typically above 0.
Must be an integer in text.
network: The network the nft will be minted on.
Should be one of MAINNET, RINKEBY, BSC, BSCTEST, or GOERLI in text.
Network should match the network the contract address is on.
image: The FILE NAME of the image file with the extension included.
Recommands dimensions 500 x 500 px due to ui nft cards displaying images as squares.
10 mb file size limit due to ipfs limitations.
Accepts jpg, png, and gif files extensions (other file extensions is allowed but may not upload/display correctly).
Used for nft cards and on nft details page as the nft profile picture.
isFeatured: Marks nft as featured.
Must be either TRUE or FALSE exactly.
Used to indicate if it is used in the featured carousel in the ui.
isTrending: Marks nft as trending.
Must be either TRUE or FALSE exactly.
Used to indicate if it is used in the trending carousel in the ui.
Optional Columns
unlockableContent: Text shown under the unlockable content of a nft.
Content here overrides collection unlockable content.
Displayed on the nft details page in the ui.
Animation: The FILE NAME of the animation file with the extension included.
10 mb file size limit due to s3 limitations.
Accepts mp4 or gif file extensions (other file extensions is allowed but may not upload/display correctly).
The animation file is used in place of the image file on the nft details page.
Project ID: Unqiue id of an associated project entry.
This id must be a valid entry on the project table or created at Projects/New if it does not exist.
These id(s) can be found under Projects/List.
Metadata: The pre-generated metadata of the nft in JSON text.
The metadata is typically automatically generated based on other inputs you entered in the backend, but if needed, you may enter your own pre generated metadata.
Accepts JSON text.
Refer to https://docs.opensea.io/docs/metadata-standards#metadata-structure for details regarding its structure.
Attributes: Additional attributes of nft outside of ones generated by the metadata.
The attributes is typically automatically generated based on other inputs you entered in the backend, but if needed, you may add additional attributes.
Accepts JSON text.
Refer to https://docs.opensea.io/docs/metadata-standards#attributes for details on formating.
Properties: additional properties of nft outside of ones generated by the metadata
The properties is typically automatically generated based on other inputs you entered in the backend, but if needed, you may add additional properties.
Accepts JSON text.
Additional Fields: Additional main properties of metadata you would like to include.
The fields is typically automatically generated based on other inputs you entered in the backend, but if needed, you may add additional fields.
Accepts JSON text.
Refer to https://docs.opensea.io/docs/metadata-standards#metadata-structure for details regarding its structure.
Criteria when minting nfts
Wallet must be connected to the network the nft draft is specified on.
The connected wallet address must be allowed to mint using the specified contract address. Typically the owner of the contract is allowed. Please refer to the deployed contract if unsure.
If batch minting, all contract addresses of the selected draft entries must be the same.
If minting an ERC721 contract, you may enter different recipients for each draft nft entry but the amount can only be 1.
If minting an ERC1155 contract, you may only enter one recipients for each draft nft entry but the amount can only be manually set.
Flow
View the Marketplace Contracts tab and record the contract address you wish to use to draft your nft. You can also create a collection under the Collection/New tab, and whitelist it under the Marketplace Contracts/New tab.
Go to NFTs/Single NFT Draft and fill out the form as per the specification.
Clicking Save Changes will save the entry to the backend
Clicking View Preview will generate an approximate ui preview of the page
Clicking Cancel will return to the launchpad list page
When saving changes, most text data will be directly transfered to the backend while images are first uploaded to S3 via a signed url. The image upload process is as follows:
The frontend will request the backend for a signed url to upload to.
The backend provides will respond with a created file entry with the upload url to the frontend.
The frontend uploads the image to the upload url.
The file entry's id will then be used to along with the rest of the inputed data to create a launchpad entry. During this process, the backend will download the image file from s3 and upload it to ipfs as well for block chain usage.
The entries can then be viewed, edited, or deleted at NFTs/List.
After drafting the nft(s), you can mint under the mint tab by following the specifications listed previously.
When minting, each nft is minted in accordance to their contract address type's protocol (ERC721 or ERC1155) and the backend will update the status of each nft to MINTED.
The minted nfts can then be viewed at NFTs/List but cannot be edited or deleted through the ui after minting.
Alternatively, steps 2 and 3 can be replaced with the following if choosing to batch mint instead.
Go to NFTs/Batch NFT Draft and upload the CSV and other assets as per the specification.
Clicking Batch Create will save the entries to the backend
After uploading, each row in the CSV file will be parsed and runs through a series of diagnostic for common errors. Refer to code for details. Afterwards, when saving to the backend, the nft data entry will be saved to the backend one row at a time using the same process step 3 is using. On screen a modal will keep track of the progress and report any rows that did not save correctly.
Last updated