hashlips_art_engine VS hashlips_art_engine

Hi. I wanted to create my own NFT collection, so I discovered this tool called HashLips : https://github.com/HashLips/hashlips_art_engine

Dear NFT community, I want you to know how much the web3 space has changed my outlook on life and it is all due to this 200-line open-source (hashlips_art_engine) code I wrote a year ago. https://github.com/HashLips/hashlips_art_engine

You’d export all the layers and variations and use a tool like https://github.com/HashLips/hashlips_art_engine to compose them into complete images.

We generate the collection images and metadata with Hashlips art engine. Clone the repository https://github.com/HashLips/hashlips_art_engine and install the dependencies.

I basically found this image generator online at https://github.com/HashLips/hashlips_art_engine which allows me to input custom layers and generate an output of random images in the project folder.

The the regenerative art engine is not used anymore. Switch to this instead: https://github.com/HashLips/hashlips_art_engine

Hashlips Art Engine https://github.com/HashLips/hashlips_art_engine

I would clone the repo and follow the instructions provided.

Fork the GitHub Repo here: NFT Generator

In my previous blog post, I put together a truffle project that could deploy ERC-721 token contracts to Polygon's Mumbai test network for compatibility for OpenSea. Today, I am ready to improve on this and show you devs and artists a couple of repositories that will help when deploying NFTs. Since my first post, I have been talking to a client about the power of regenerative art. Where artists can save time designing thousands of NFTs. I did some digging, and with some help from Moralis YT and HashLips GitHub, I conjured up a couple repos. Unfortunately, I have not configured an ERC-1155 example yet, but it is not too dissimilar from this code. So let's see what improvements I have made from the previous ERC-721 boilerplate.

Forked HashLips art engine for IPFS uploads