To find out more about The Peanut Gallery And Co, please visit:
Base code is from the below repos - Massive thank you to the teams behind these repos!
- hashlips_art_engine
- codeSTACKr
- Gerhard Molin - Provenance Addition
- Arnau González - Exclusions Addition
- Andy Jiang Pro - Opensea Metadata Refresh
File Uploads can be done via Pinata or a similar service that gives you a single CID for images and another one for meta files or NFTPort can be used.
Minting uses NFTPort
Please note that some of the commands have changed and have been updated compared to the original videos, please see them under the different sections for each script / process that you can run.
If you feel that this has benefitted you in any way and would like to make a contribution towards The Peanut Gallery And Co, then please use the following MetaMask wallet address:
0x5cE5D823f4bD8Ec610868fBa65832B479152C7E1
If you would like to support my NFT collection, please take a look at the below.
npm install
Please note that if you have a Mac with a M1 chip and you run into issues with npm install, then please try to install Node.js version 14 instead of the latest Node version and try the npm install again
- Updates & Fixes
- How To Use The Codebase
- 1. Download and unzip the main branch of this repo
- 2. Run the dependency npm commands in the unzipped folder
- 3. Update The Main Configuration File For The Art Engine
- a. If you are planning on using Solana, then update this section
- b. Update your layer configurations
- c. Update the width and height of your canvas
- d. Update the extra metadata that you want to add into your NFT's metadata. You can remove both fields inside of this extraMetadata object or add more if you like
- 4. Configure The NFT Creation Details
- 5. Configure The NFTPort Account Details And API Limits - Only modify this if you are using NFTPort for uploading
- 6. Create Image Layers
- 7. Art Engine
- 8. Update NFT's Info (Description And Name)
- 9. Update NFTs For Reveal - Generic Image Until Purchased, Then Only Reveal NFT
- 10. Uploading Files (Images and Metadata)
- 11. Create Wallet Edition Combo
- 12. ERC1155 Batch IPFS Metas Migration
- 13. Minting NFTs
- 14. Checking NFT Mint Files For Issues
- 15. Re-Mint Failed NFTs
- 16. Check Your Work On The Marketplace
- 17. Refresh NFT Metadata For Opensea
- 18. Sell NFTs Opensea
-
- Download Repo And Extract
- Install Packages
- Update src/config.js
- Update constants/account_details.js
- Update constants/nft_details.js
- Art Engine - Build
- Update JSON To Generic Meta
- Upload Files
- Upload Metas (NFTPort - UploadMetas Command) - This will upload your json directory's files
- Rename ipfsMetas directory
- Update constants/account_details.js
- Upload Metas (NFTPort - UploadMetas Command) - This will upload your genericJSON directory's files
- Mint - This will mint your unrevealed NFTs' metadata
- Manually Update Metadata After Purchase
-
- Download Repo And Extract
- Install Packages
- Update src/config.js
- Update constants/account_details.js
- Update constants/nft_details.js
- Art Engine - Build
- Update JSON To Generic Meta
- Upload Files
- Upload Metas (NFTPort - UploadMetas Command) - This will upload your json directory's files
- Rename ipfsMetas directory
- Update constants/account_details.js
- Upload Metas (NFTPort - UploadMetas Command) - This will upload your genericJSON directory's files
- Batch IPFS Metas Migration
- Mint Batch - This will mint your unrevealed NFTs' metadata
- Manually Update Metadata After Purchase
- EXAMPLE - DNA EXISTS AND NEED MORE LAYERS TO GROW EDITION
- EXAMPLE - FILE ALREADY UPLOADED
- EXAMPLE - UPLOAD GENERIC METAS WITHOUT CREATING GENERIC METAS FILES
- EXAMPLE - METADATA ALREADY UPLOADED OUTPUT
- EXAMPLE - MINT FAILED, USING CHECK_MINTS AND REMINT
- EXAMPLE - MINT BATCH FAILED, USING CHECK_MINTS_BATCH AND REMINT_BATCH
- EXAMPLE - EDITION ALREADY MINTED
- EXAMPLE - CONTRACT ALREADY HAS THE GIVEN TOKEN ID
Added a new script utils/opensea/sell_nfts.js that will allow users to sell NFTs between two edition numbers (inclusive) to be put up for sale if the user owns the NFTs. This functionality uses Puppeteer and Chainsafe's Dappeteer, so please use at your own discretion as you will need to make use of your private key for this functionality to work.
- Feature - Opensea Polygon Script To Auto Sell NFTs
- Feature - Opensea Polygon Script To Auto Sell NFTs Additional Fields
- Feature - Opensea Polygon Script To Auto Sell NFTs Added Metamask Account Number
- Feature - Opensea Sell Script Support Different Currency Selection
Added a new script utils/opensea/cancel_on_sale_nfts.js that will allow users to remove NFTs that they own from being on sale between two edition numbers (inclusive). This functionality uses Puppeteer and Chainsafe's Dappeteer, so please use at your own discretion as you will need to make use of your private key for this functionality to work. Feature - Cancel NFTs On Sale On Opensea
Added a new layerItemsMaxRepeatedTrait setting that can be used to set the maximum repeatability for all items within a layer. If this is set to 2 for example and your layer has 8 layer items, then a maximum of 16 images will be generated. This allows users to set the maximum repeatability once off for a layer's items instead of specifying each layer item with the same maximum repeatability. Feature - Add Maximum Repeatability For All Items In A Layer In A Single Configuration
Below is a rough guideline of the order in which the processes can be used.
Please note that when extracting the code base, there's two possibilities for the extracted folder. Please always make sure that you are opening the folder in VS Code or your terminal which matches the folder structure in step 2.
If this is the case when extracting your folder, then be sure to "cd" or move into that folder before running step 2's install commands, otherwise you will receive module errors and the npm installs won't work and your build and upload commands will not work correctly.
No need for any extra steps, you can start with step 2 where you run the npm install commands.
Ensure that you are in this diretory before running the npm install commands, otherwise some of your commands will not work correctly.
Example of the contents of the root folder before running the installs:
Example of the contents of the root folder after running the installs:
Update the src/config.js file with the different settings for your generative art collection.
Please watch the videos linked earlier on how to configure the Art Engine.
Modify the following parts at the very least, below are just sample values that I used in a demo.
- Update your folder names, order in which they need to be processed and the number of images to create
- Optionally add maximum repeatability filtration rule in for the layers - Please see Maximum Repeatability Feature and Layer Item Maximum Repeatability Settings and Add Maximum Repeatability For All Items In A Layer In A Single Configuration
- Optionally add layer combination filtration rules in for the layers - Please see Layer Combination Exclusion Feature
- Optionally add layer dependent traits filtration rules in for the layers - Please see Layer Trait Dependencies Feature
Example of default configuration along with maximum repeatability and layer compatibility
d. Update the extra metadata that you want to add into your NFT's metadata. You can remove both fields inside of this extraMetadata object or add more if you like
Update the constants/nft_details.js file with the details that you want to be added to your metadata for your generative art collection.
description- The description that will be added to each of your NFTsnamePrefix- The name prefix that will be added for each of your NFTs. Ex. Steaks #1, Steaks #2imageFilesBase- Pinned IPFS CID when making use of a service like Pinata. Ex. QmP12prm2rp1omr1Ap2orm1oprm12FQWFQOFOGdnasnsda . Only update this if you are planning to upload the files via a service other than NFTPort where you host a single URL / CID base.metaDataJSONFilesBase- Pinned IPFS CID when making use of a service like Pinata. Ex. QmP12prm2rp1omr1Ap2orm1oprm12FQWFQOFOGdnasnsda . Only update this if you are planning to upload the files via a service other than NFTPort where you host a single URL / CID base.ignoreExactBlankName- This value is a boolean with a value of false or true. If true, then any layer that contains only the name "blank" with a rarity character and value in the metadata will be skipped and not added to the properties of the NFT. When set to false, then the information will be added to the metadata and added to the properties of the NFT.genericTitle- Replace with what you want the generic titles to say. Only change if you are planning on using NFT reveal and want a different name for your NFTs.genericDescription- Replace with what you want the generic descriptions to say. Only change if you are planning on using NFT reveal and want a different name for your NFTs.genericURLs- Replace with the image URLs that your generic NFTs should show. Only change if you are planning on using NFT reveal and want a different name for your NFTs.ignoreAllNamesWithBlank- This value is a boolean with a value of false or true. If true, then any layer item that contains the word blank within the filename will be skipped from being added to the metadata information. When set to false, then the information will be added to the metadata. E.x white_eyes_blank #100.png will be added to metadata if set to false, while being skipped if true.startCollectionEditionFrom- This value is used to determine from which edition number the collection creation should start. It is set to'1'as default, which will start Sol collections at 0, while starting Eth collections at 1. If you plan on using Collection contracts from NFTPort, then be sure to set this value to'0'before generating your art work.
Modify only the parts that you will be using and keep the rest as set by default.
For example, if you are planning on using NFTPort for your file and metadata uploads, then do not modify the imageFilesBase and metaDataJSONFilesBase fields. If you are planning on not doing a reveal NFT collection and simply have everything revealed, then do not modify the genericTitle, genericDescription and genericURLs fields. If you want your NFT properties on Opensea to show, for example "Blank #15.png", then set the ignoreExactBlankName value to false. If you want to remove all "blank" layer items from your NFT properties on Opensea, for example "white_eyes_blank #10.png", then set the ignoreAllNamesWithBlank value to true.
Example configuration:
5. Configure The NFTPort Account Details And API Limits - Only modify this if you are using NFTPort for uploading
Update the constants/account_details.js file with the NFTPort account details. These will only be used with the NFTPort scripts. This will be needed if you are uploading files or minting via NFTPort. Please ensure that your NFT contract was created with the metadata_updatable variable set to true as this allows for NFT metadata updates to be made and is needed if you are planning on doing NFT reveals after purchases. If not, then you can't change your NFT data and you will need to burn the NFT from the contract to remove it. This will cost you funds / tokens, so make sure you create your contract correctly!
auth- Add your APIKey here that the NFTPort team will provide. Ex. orm1or1-efe1-112a-cccd-kqwfkfmkcontract_address- Add your contract address here, not your transaction hash. After creating a contract on NFTPort, retrieve the contract address via the APIs. Ex. 0xfe81cm1l28b21753ebe117c84als2d6588e150ffmint_to_address- Add your wallet address here that will be the owner of the minted NFTs. Ex. 0x5cE5D823f4bD8Ec610293fBa65832B479152C7E1chain- Add the chain where the NFTs will be minted to here. At the time of writing, "polygon" and "rinkeby" are possible values.max_rate_limit- This will rate limit your API calls towards the NFTPort platform. Be sure to set it according to what is allowed for your APIKey. Ex. '1'numberOfRetries- This is the retry count that your NFTPort API calls will attempt when not receiving a successful response from the API. It is not advised to make the retry count too high. Ex. '3'timeout- This is the waiting time in between API calls when errors arise on the APIs. This has been disabled at the moment as it causes the scripts to hang at times. E.x. 5000 = 5 seconds.mint_range- If you only want to mint a specific range of editions, e.x everything between editions 5 and 10.mint_item- If you only want to mint a specific edition, e.x 1.uploadGenericMeta- If you are planning on using a reveal, then set this value to true, otherwise keep this as false. When it is true, then the uploadMetas files will read from the genericJSON directory to upload the metadata. If set to false (default), then it will read from the json directory which contains your revealed items.batch_mint_size- The number of NFTs that are minted per batch_mint. Maximum is 50 NFTs per batch_mint. This is only applicable to ERC1155 contracts, not ERC721.batch_mint_nft_amount- The number of times that each NFT will be minted. For example, if set to 5, then each NFT edition can be sold 5 times. This is only applicable to ERC1155 contracts, not ERC721.
Modify only the parts that you will be using and keep the rest as set by default.
For example, if you are having issues and want more retries on the API or a higher rate limit, only then modify those fields. If you are planning on only minting a single edition or a range of editions, only then modify those fields. If you are planning on doing a reveal, only then modify the uploadGenericMeta field. If you are making use of ERC1155 contract, then update the batch_mint_size and batch_mint_nft_amount fields to change the number of NFTs per mint and the number of times that each NFT can be sold for.
Example configuration:
Create your different art layers, keeping all of them at the same Canvas size and ensuring they are all exported as .png files.
Review the Hashlips videos on what all of the configuration items in the src/config.js file means and what you need to set them to.
All of the Art Engine Commands make use of this configuration file along with the constants/nft_details.js file.
Only run the commands from sections a, b and c that you would like to make use of.
Use the Art Engine - Build Command below to create your generative art collection along with their metadata json files.
- Use the
Art Engine - Pixelate Commandbelow to create a pixelated art collection from your previous generative art collection. - Use the
Art Engine - Preview Commandbelow to create a preview of your generative art collection by combining a few of the images into a single image. - Use the
Art Engine - Preview_Gif Commandbelow to create a preview_gif of your generative art collection by combining a few of the images into a single gif that loops through some of your images.
Use the Art Engine - Rarity Command below to generate a JSON output to the terminal that will show you how your layers will be distributed.
Use the Custom - Rarity_Md Command below to generate a JSON file (_metadata_with_rarity.json) in the build/json/ directory. This will add a rarity_score key to each attribute as well as a total_rarity_score and rank for each NFT edition. Use the Custom - Rarity_Rank Command below to pull information from the _metadata_with_rarity.json file, like the top X editions or the rank of a specific NFT edition.
Example of top 20 editions from my collection
create-and-mint-nft-collection roebou$ npm run rarity_rank
> [email protected] rarity_rank
> node utils/custom/rarity_rank.js
Enter 1 to get top ## NFTs by rarity or 2 to get a specific NFTs rarity: 1
Enter the number of NFTs you want to get: 20
[
{ name: 'Steak Bite #8237', rank: 1, total_rarity_score: 110.84 },
{ name: 'Steak Bite #5552', rank: 2, total_rarity_score: 110.66 },
{ name: 'Steak Bite #342', rank: 3, total_rarity_score: 105.64 },
{ name: 'Steak Bite #7612', rank: 4, total_rarity_score: 105.08 },
{ name: 'Steak Bite #5086', rank: 5, total_rarity_score: 103.83 },
{ name: 'Steak Bite #1093', rank: 6, total_rarity_score: 103.45 },
{ name: 'Steak Bite #2898', rank: 7, total_rarity_score: 101.94 },
{ name: 'Steak Bite #3326', rank: 8, total_rarity_score: 100.11 },
{ name: 'Steak Bite #4257', rank: 9, total_rarity_score: 98.16 },
{ name: 'Steak Bite #435', rank: 10, total_rarity_score: 96.26 },
{ name: 'Steak Bite #8675', rank: 11, total_rarity_score: 96.06 },
{ name: 'Steak Bite #1288', rank: 12, total_rarity_score: 95.43 },
{ name: 'Steak Bite #2966', rank: 13, total_rarity_score: 95.16 },
{ name: 'Steak Bite #7232', rank: 14, total_rarity_score: 95 },
{ name: 'Steak Bite #9128', rank: 15, total_rarity_score: 94.62 },
{ name: 'Steak Bite #6542', rank: 16, total_rarity_score: 94.58 },
{ name: 'Steak Bite #3942', rank: 17, total_rarity_score: 94.52 },
{ name: 'Steak Bite #9162', rank: 18, total_rarity_score: 94.41 },
{ name: 'Steak Bite #3864', rank: 19, total_rarity_score: 93.61 },
{ name: 'Steak Bite #1150', rank: 20, total_rarity_score: 93.46 }
]
create-and-mint-nft-collection roebou$
Use the Art Engine - Create_Provenance Command below to generate two new JSON files within the build/json directory. To read up more on Provenance and how it can be used in your NFT Collections, please see the following Medium Link
concatedHash.json- This is a string that contains the concated hash string of all image URIs.provenanceHash.json- This is the final proof of your collection. This is a hash based on theconcatedHash.jsonfile's contents.
provenanceHash.json structure:
{
"provenance": "",
collection: [
{
"tokenId": ,
"image": "",
"imageHash": "",
"traits": [],
}],
}Use the Art Engine - Generate_Metadata Command below to generate a json file for each of the image files in the build/images folder.
Please use this with caution as this will delete your build/json directory and generate a new directory with new files in it. If you would like to test this out, please be sure to backup your build/json directory first if you have one.
Use the Custom - Update_Nft_Info Command below to update all NFT JSON files with the new namePrefix and description from the constants/nft_details.js file.
Please note that this should be run before you run the NFTPort - UploadFiles Command, NFTPORT - UploadMetas Command, NFTPORT - UploadMetas_Directory Command and NFTPORT - Mint Command commands.
Use this only if you want to use a different name and description for your NFTs compared to what got generated with the Art Engine - Build Command command.
Use the Custom - Update_Json_To_Generic_Meta Command below to update all NFT files with the genericTitle, genericDescription and genericURLs values set in the constants/nft_details.js file. This will be shown as your NFT's details and picture before a purchase.
This process will create a new genericJSON directory where the _metadata.json file will be located along with each file's generic JSON object file. Remember to change your uploadGenericMeta key's value to true in the constants/account_details.js file before making use of the UploadMetas and UploadMetas_Directory scripts so that it will upload the files in this directory instead of the normal json directory if you are making use of reveals.
Please remember that your contract needs to be updateable to use this, otherwise this image will stay the image of your NFT, before and after purchase.
Please remember to update the genericURLs field with the URLs where the generic images are located. You can upload your generic image files to IPFS by simply using the NFTPort API via the frontend to upload a file and receive an IPFS URL that you can use within the genericURLs field.
There are two options that you can follow to upload your images and json files onto IPFS. Option 1 would be to go via a service like Pinata that gives a static CID to be used, while Option 2 would be to go directly via NFTPort, however, the CID will be unique for each file.
Create an account on Pinata and then upload your images folder. Please note that once you have uploaded your folder, you can't add or remove any files from there. From there copy the CID into the constants/nft_details.js file against the imageFilesBase key.
Use the Custom - Update_Image_Info Command below to update the json files for each NFT.
This process will only update the file_url and image fields within the json file as well as in the _metadata.json file.
Upload the json directory onto Pinata and copy the CID into the constants/nft_details.js file against the metaDataJSONFilesBase key. This should be either of your json or genericJSON directories, depending on whether you are doing a reveal or not. Just a note, it would make sense to get both of your json directories uploaded if you are doing a reveal so that you can simply update the metadata of your unrevealed NFT, but please see the section on NFT reveal steps to follow in the EXAMPLE - REVEAL (ERC721) and EXAMPLE - REVEAL (ERC1155) examples below.
Use the Custom - Update_Metadata_Info Command below to update the json files for each NFT.
This process will create a new ipfsMetas folder, update each NFT json file with a metadata_uri field and create a _ipfsMetas.json file. All the new json files will be added to the ipfsMetas folder.
Create an account on NFTPort and get an APIKey. Be sure to check your rate limit of your account as well as the amount of NFTs that you can upload with your APIKey's access levels. Update your account's details in the constants/account_details.js file.
Use the NFTPort - UploadFiles Command below to upload the image files to IPFS. This process will also update the json file for each NFT with the IPFS URL and add it into the file_url and image fields. This process will only update the file_url and image fields within the json file as well as the corresponding object in the _metadata.json file.
Use the NFTPort - UploadMetas Command or NFTPORT - UploadMetas_Directory Command below to upload the json metadata files for each NFT to IPFS and then create a ipfsMetas folder with an _ipfsMetas.json file and a json file for every NFT, containing the upload API response.
The new json files in the ipfsMetas directory will now contain a metadata_uri field and this has also been added to each object inside the _ipfsMetas.json file.
Important - Should you wish to do a reveal, please remember that your contract should allow for updates to your NFT files. You also need to update the uploadGenericMeta key's value to true in the constants/account_details.js file so that the genericJSON directory's metadata will be used instead of the json directory. Please see the section on NFT reveal steps to follow in the EXAMPLE - REVEAL (ERC721) and EXAMPLE - REVEAL (ERC1155) examples below.
If you would like to mint your editions to different wallets, then you need to populate the account_details.js file's walletMintList with the wallet address and nft edition count. Once this is done, then run the Custom - Create_Wallet_Edition_Combo Command, which will generate a new _walletAddressMintList.json in the ipfsMetas directory. When you run the the ERC1155 Batch IPFS Metas Migration or Minting NFTs steps, then it will attempt to get the specific edition's wallet address that it needs to mint towards. If it can't find the _walletAddressMintList.json file or the edition is not in the file, then the mint process will default back to the mint_to_address field in the account_details.js file.
If you would like to make use of batch minting against an ERC1155 contract, you need to run the Custom - Batch_Ipfs_Metas_Migration script which will create a new batchIPFSMetas directory and it will create numbered json files, for example 1.json which will contain a list of tokens for that specific batch to be minted, and a new _batchIPFSMetas.json file which will be a combined json file of all the numbered json files. The NFTPort - Mint_Batch Command will use this file these files to mint the token batches.
Before you use the Custom - Batch_Ipfs_Metas_Migration script, please be sure to update the batch_mint_size and batch_mint_nft_amount key's values to what your requirement is. By default, it is set to 50 for the batch_mint_size key and 1 for the batch_mint_nft_amount key.
- Use the
NFTPort - Mint_Batch Commandbelow to start minting against an ERC1155 contract where your mints will happen in batches. - Use the
NFTPort - Mint Commandbelow to start minting against an ERC721 contract where your mint will happen individually. - Use the
NFTPort - Mint_Range Commandbelow to start minting against an ERC721 contract for a range of NFTs between specific editions. - Use the
NFTPort - Mint_Item Commandbelow to start minting against an ERC721 contract for a specific NFT edition.
Before you use the NFTPort - Mint_Range Command script, please be sure to update the mint_range key's values to the from and to edition numbers that you would like to attempt to mint. Please note that both of these numbers are inclusive.
Before you use the NFTPort - Mint_Item Command script, please be sure to update the mint_item key's values to the edition number that you would like to attempt to mint.
Before you use the NFTPort - Mint_Batch Command script, please be sure to run the Custom - Batch_Ipfs_Metas_Migration script.
- Use the
Custom - Check_Mints Commandbelow to start checking each mint file to determine if there are any issues with the minted files for ERC721 contract files (individual files). - Use the
Custom - Check_Mints_Batch Commandbelow to start checking each mint file to determine if there are any issues with the minted files for ERC1155 contract files (batch files).
The check performs validation of the issues experienced in the Minting NFTs section and writes out the json files into a failedMints directory.
The checks that this script performs to determine if a NFT mint has failed are done in all of the minting scripts before a mint is attempted for a specific file. The reason for adding this script is so that if you have 10 000 NFTs that you minted and you simply run one of the minting scripts again, then it will first scan the relevant file (depending on the mint command used) and then perform mint. This means if you use the mint script again, it will go through all 10 000 items, every time you run it. Should you use batch minting, then less files will be scanned, depending on your batch sizes.
The check mints scripts will go through the files once off, check all of their data and provide a list of items that need to be re-minted with the NFTPort - Remint Command or NFTPort - Remint_Batch Command, which will only scan the files that got picked up by the check mints processes.
Please note that every time this runs, it clears out the folder and starts again.
Please note that this process can take time to complete as it runs through every minted json file.
- Use the
NFTPort - ReMint Commandbelow to start re-minting each of the json files in thefailedMintsdirectory for ERC721 (Individual files) contract files. - Use the
NFTPort - ReMint_Batch Commandbelow to start re-minting each of the json files in thefailedMintsdirectory for ERC1155 (batch files) contract files.
This process will write out a newly minted file in the reMinted directory as well as update the json file in the original minted directory. Due to this, a backup folder will be created every time this process runs with the date to keep a backup of the json file in the minted directory at the time of running this process just as a safe guard so that you have access to the original information or how the information changed in between your processing.
You are done with your minting process! Well done! Go and check out your mints on your marketplace and refresh the metadata where needde.
GOOD LUCK!
Go to the utils/opensea/refresh_metadata.js file and update the START_EDITION and END_EDITION fields. Please make sure that the contract address that you are trying refresh has been set for the contract_address field in the constants/account_details.js file.
Use the Opensea - Refresh_Metadata Command below to start the refresh of metadata for each NFT edition between your start and end editions.
Please note this process will be time consuming for large editions.
Selling NFTs
Go to the utils/opensea/sell_nfts.js file and update the START_EDITION, END_EDITION, NFT_PRICE, DROPDOWN_OPTION, DATE_PICK_SKIP, START_HOUR, START_MINUTE, END_HOUR, END_MINUTE and walletPrivateKey fields. Please make sure that the contract address that you are trying sell NFTs for has been set in the contract_address field in the constants/account_details.js file as well as that the chain value is correct for the specific contract address.
Use the Opensea - Sell_Nfts Command below to start the putting each NFT edition up for sale between your start and end editions for the given price.
Cancel On Sale NFTs
Go to the utils/opensea/cancel_on_sale_nfts.js file and update the START_EDITION, END_EDITION and walletPrivateKey fields. Please make sure that the contract address that you are trying cancel the sale of NFTs for has been set in the contract_address field in the constants/account_details.js file as well as that the chain value is correct for the specific contract address.
Use the Opensea - Cancel_On_Sale_Nfts Command below to start the removing each NFT edition from being on sale between your start and end editions.
Features:
- Feature - Opensea Polygon Script To Auto Sell NFTs
- Feature - Opensea Polygon Script - To Auto Sell NFTs Additional Fields
- Feature - Opensea Polygon Script To Auto Sell NFTs Added Metamask Account Number
- Feature - Cancel NFTs On Sale On Opensea
Please read the warning very carefully within the the sell_nfts.js and cancel_on_sale_nfts.js files with regards to the walletPrivateKey field. Please note that this script will only work with the Polygon network Please note this process will be time consuming for large editions.
- npm run build
- npm run create_provenance
- node utils/art_engine/create_provenance.js
- npm run generate_metadata
- node utils/art_engine/generate_metadata.js
- node utils/art_engine/pixelate.js
- npm run pixelate
- node utils/art_engine/preview.js
- npm run preview
- node utils/art_engine/preview_gif.js
- npm run preview_gif
- node utils/art_engine/rarity.js
- npm run rarity
Use the following command from the code's root directory.
- node utils/custom/batch_ipfs_metas_migration.js
- npm run batch_ipfs_metas_migration
- node utils/custom/check_mints.js
- npm run check_mints
- node utils/custom/check_mints_batch.js
- npm run check_mints_batch
- node utils/custom/create_wallet_edition_combo.js
- npm run create_wallet_edition_combo
- node utils/custom/getRarity_fromMetadata.js
- npm run rarity_md
- node utils/custom/rarity_rank.js
- npm run rarity_rank
- node utils/custom/update_image_info.js
- npm run update_image_info
- node utils/custom/update_json_to_generic_meta.js
- npm run update_json_to_generic_meta
- node utils/custom/update_metadata_info.js
- npm run update_metadata_info
- node utils/custom/update_nft_info.js
- npm run update_nft_info
Use the following command from the code's root directory.
- node utils/nftport/mint_batch.js
- npm run mint_batch
- node utils/nftport/mint_item.js
- npm run mint_item
- node utils/nftport/mint_range.js
- npm run mint_range
- node utils/nftport/mint.js
- npm run mint
- node utils/nftport/remint.js
- npm run remint
- node utils/nftport/remint_batch.js
- npm run remint_batch
- node utils/nftport/reveal.js
- npm run reveal
- node utils/nftport/uploadFiles.js
- npm run uploadFiles
- node utils/nftport/uploadMetas.js
- npm run uploadMetas
- node utils/nftport/uploadMetas_directory.js
- npm run uploadMetas_directory
Use the following command from the code's root directory.
- node utils/opensea/cancel_on_sale_nfts.js
- npm run cancel_on_sale_nfts
- node utils/opensea/refresh_metadata.js
- npm run refresh_metadata
- node utils/opensea/sell_nfts.js
- npm run sell_nfts
Make sure that your uploadGenericMeta key's value is set to false initially and that your contract's metadata_updatable value is set to true.
This script will utilize the generic field's values set in the constants/nft_details.js file and create a new genericJSON directory which will contain the metadata that you want to mint for the unrevealed NFTs. Ensure that you have updated the generic fields within the constants/nft_details.js file before running the script as it will use these fields to build the new generic json files.
Rename the ipfsMetas directory to realIPFSMetas or anything other than ipfsMetas as these are the files to be used for revealing your data after purchases.
Update your uploadGenericMeta key's value to true.
Once your NFT has sold, go to NFTPort and go to the docs / API section. From there, go to the Minting section and choose the Update a minted NFT API. Take the packet on the API's right hand side and update it with the details from your unrevealed folder. (realIPFSMetas or whatever you called your backup folder)
Send the API request on the right hand side and if all goes well, then your NFT's metadata will now be updated and the revealed image will show.
Please note that if you want to freeze the metadata so that no more updates can happen, then include the optional freeze_metadata: true field and key to the json packet that you will send in the API call
Make sure that your uploadGenericMeta key's value is set to false initially and that your contract's metadata_updatable value is set to true.
This script will utilize the generic field's values set in the constants/nft_details.js file and create a new genericJSON directory which will contain the metadata that you want to mint for the unrevealed NFTs. Ensure that you have updated the generic fields within the constants/nft_details.js file before running the script as it will use these fields to build the new generic json files.
Rename the ipfsMetas directory to realIPFSMetas or anything other than ipfsMetas as these are the files to be used for revealing your data after purchases.
Update your uploadGenericMeta key's value to true.
Once your NFT has sold, go to NFTPort and go to the docs / API section. From there, go to the Minting section and choose the Update a minted NFT API. Take the packet on the API's right hand side and update it with the details from your unrevealed folder. (realIPFSMetas or whatever you called your backup folder)
Send the API request on the right hand side and if all goes well, then your NFT's metadata will now be updated and the revealed image will show.
Please note that if you want to freeze the metadata so that no more updates can happen, then include the optional freeze_metadata: true field and key to the json packet that you will send in the API call
When you encounter DNA exists!, do not panic as this simply means the combination of elements have already created an image and it will try a different combination. If you encounter You need more layers or elements to grow your edition to 20 artworks!, with 20 being the number of NFTs you are trying to generate, then it simply means you do not have enough unique items within your layers to create the total number of NFTs that you are trying to create. You need to add more items to your layers, so maybe add a blank image so that your layers only sometimes populate. Another item that you can look to modify when you are working with big collections is the uniqueDnaTorrance setting in the src/config.js file. This is set to 10000 by default, but if you might need to make that a higher number and try to generate your collection again. For demo purposes, I set my uniqueDnaTorrance to 2 to for demo purposes to trigger the error.
When you encounter 5 already uploaded. error in the uploadFiles script, it means that your json file already contains a https://xxxx URL for the file_url key. If you would really like to re-upload the image, simply remove the URL value (not the whole line, just the value, otherwise you will see an error if the field key is not there) or change it to IPFS, then run the uploadFiles script again and the files will be re-uploaded.
When you are trying to upload your metadata files via the uploadMetas script, but you haven't run the update_json_to_generic_meta script before attempting the upload, then the below error will be seen as no genericJSON directory can be found.
This means the edition number of the token that you are trying to mint already exists against your contract. Go to your contract address on your chain's explorer and you should see that the tokenid is already there.
Please note that there is no need to panic as you can't upload the same tokenid against a given contract, so you won't have any duplicates.
