NFT Metadata

As part of ERC721 and the extended OpenSea NFT specification, there are a few fields we surface in our default Tap Experience from the metadata JSON file.
  • name - title of your item
  • description - description of your item, supports markdown format
  • image - the http/s URL to your hosted image
  • animation_url - the http/s URL to your hosted video (animation will display instead of image when available)
"name": "Legitimate Demo Item",
"description": "Loreum ipsum description text",
"animation_url": "",
"image": ""

Pre-reveal Metadata

The locking mechanism in the LGT Protocol allows a separate set of metadata to be displayed when the NFT has not been claimed, or has been transferred to a new owner but has not been unlocked yet by the new owner. A separate set of metadata allows the owner and the public to differentiate between the locked and unlocked states of the NFT visually. The same pre-reveal metadata must be used for all items in the collection.
Our clients often choose to use a blurred or greyscale NFT image, or a lock indicator for the pre-reveal image.
Most of our clients also choose to include the token ID in the title after the reveal to show the limited quantity and uniqueness of the item.
Pre-reveal NFT metadata example:
NFT metadata example:

IPFS File Pinning and Content Optimization

Legitimate uses Pinata for IPFS file pinning and content delivery. When images are hosted by Legitimate, they will be automatically optimized and resized for different device screen sizes and file format capabilities and served from a global gateway CDN. Animation videos will stream and autoplay muted in the Tap Experience.
An example of a full set of metadata is available on GitHub.
See NFT Image Specs and NFT Animation Specs for more details on file formats.