Can the CID be generated and included in the metadata?
alblunty opened this issue · comments
Can the CID be generated and included in the metadata?
So it can be used with IPFS.
Is it already included, or am I missing something?
Did we get a consensus on this?
This app could upload the images and json with the descriptions in a pre-defined location... Then, we would need just the metamask connector to choose which blockchain to publish this to.... Here's what I would like:
Load Image from Github Repo
- Just using GitOps, I want to have the option of the github repo with all the images and metadata for the generation
Upload images from Local HOst or S3 bucket
- If we are generating more than 1K NFTs, it's important to load them from a remote location.
- It can be any service like AWS, Google, Azure
Load NFT images to IPFS
- Since the app has the Images and metadata, why not generating the NFTs in IPFS
- Create the folders of images
- Creste the folders of associated json file that describes the NFT asset
- This is the standard if anyone wants to trust the NFT is immutable
Use a PIn Service
- Let users choose PInata or any other Pin Service to view the art gallery
Connect a wallet through Metamask
- Let users test the process before choosing the Marketplace