Metadata Support

To ensure your collection's metadata structure abides by the ERC-721 and ERC-1155 standards, as well as the OpenSea Metadata Standards, you can follow a structure similar to the example below:

   "name": "Name of the NFT",
   "description": "Description of the NFT",
   "image": "https://example.com/image.jpg",
   "external_url": "https://docs.libera.com/3",
   "attributes": [
      {
         "trait_type": "Trait 1",
         "value": "Value 1"
      },
      {
         "trait_type": "Trait 2",
         "value": "Value 2"
      }
   ]
}

Explanation of fields:

• name: The name of the NFT.

• description: A description of the NFT.

• image: A URL pointing to the image of the NFT.

• external_url: URL appearing below the assets image.

• attributes: An array containing various attributes or traits of the NFT. Each attribute is an object with trait_type specifying the type of the attribute and value specifying its value.

You need to ensure that your contract's tokenURI() function (for ERC-721) or uri() function (for ERC-1155) returns a valid URI that points to the JSON metadata of the token. This URI can be any of the valid formats mentioned in your prompt, such as IPFS, Arweave, HTTPS, base64 encoded JSON, or UTF-8 encoded JSON.