Step 2 - Edit CSV File
In the previous step Step 1 - Initialize collection a template CSV file 00000.nfts.csv was created. The purpose of this file is to provide all necessary information for each NFT in your collection in an easy as possible way. This requires, that the artist edits the CSV file according to his NFTs. This can be done most efficiently within MS Excel, Google Spreadsheet or similar tools.
Each line within the document represents a single NFT, and a file may look like this
Column | Description | Format | Example |
name* | The Name of the NFT | String (Min: 4 Max: 32) | Cute Monstas |
description* | The Description of the NFT | String (Min: 16 Max: 512) | This is the ultimate collection of cute monstas |
symbol | A alphanumeric Symbol | String (Max: 16) | MONSTA |
edition | A alphanumeric Edition | String (Max: 24) | Season 1 |
royalties* | The royalties in percent you earn when sold | Number (Max: 25) | 10 |
identifier | Some numeric identifier, usually an incremental value | Number | 666 |
image1* | The absolute file path to the first image | String - Supported formats are PNG, JPG, WEBP, GIF, SVG | /home/ohager/Desktop/generated-cute-monstas/4.png (Posix and Windows paths are possible) |
image2 | The absolute file path to the second image | String - Supported formats are PNG, JPG, WEBP, GIF, SVG | |
image3 | The absolute file path to the third image | String - Supported formats are PNG, JPG, WEBP, GIF, SVG | |
attribute1 | The attribute/trait of the NFTs. This value is used to calculate rarities within a collection. It is a key-value tuple and each NFT can have up to eight attributes | String Pattern: key:value (separated by : ) | background:green |
attribute2 | | | |
attribute3 | | | |
attribute4 | | | |
attribute5 | | | |
attribute6 | | | |
attribute7 | | | |
attribute8 | | | |
listingMode* | The initial listing mode, i.e For Sale, For Auction, or Not For Sale | One of: FixedPrice OnAuction or NotForSale | OnAuction |
price** | Only required if listingMode is OnAuction or FixedPrice - The initial price n SIGNA Only required if listingMode is OnAuction - "Buy Now" price for auctions in SIGNA Only required if listingMode is OnAuction - "Buy Now" price for auctions in SIGNA Only required if listingMode is OnAuction | Number | 1000 |
offerPrice** | Only required if listingMode is OnAuction - "Buy Now" price for auctions in SIGNA Only required if listingMode is OnAuction Only required if listingMode is OnAuction | Number | 1500 |
auctionEnd** | Only required if listingMode is OnAuction - Date and Time when auction ends. The date will be converted in Blocktime and might result in estimated targed time. This way minute precision is not guaranteed. | Date String in ISO-Format: YYYY-MM-DDThh:mm:ssZ (best is to use UTC-00 time aka GMT) | 2022-05-30T10:00:00Z |
Editing so much data/lines can be error prone, so validation of the input data is necessary. Of course, the signumart-massup tool provides validation. Simply use the collection commit command in Trial Mode like this:
In case of errors they will be shown like in the following example:
Before you execute a command, you should select the folder in which the csv and the data are stored in the command line tool!