nft

Creating a nft infrastructure for users to mint NFTs using our drag-and-drop UI and have those NFTs be listed on our marketplace.

Resources

• zNFT-hooks
• zdk
• media-metadata-schemas

Smart Contracts

• ERC721: A standard interface for non-fungible tokens, also known as deeds.

• ERC1155: A standard interface for contracts that manage multiple token types. A single deployed contract may include any combination of fungible tokens, non-fungible tokens, or other configurations (for example, semi-fungible tokens).

• RFTs

Metadata Standards

'Providing asset metadata allows applications like OpenSea to pull in rich data for digital assets and easily display them in-app. Digital assets on a given smart contract are typically represented solely by a unique identifier (e.g., the token_id in ERC721), so metadata allows these assets to have additional properies, such as a name, description, and image.'

• https://docs.opensea.io/docs/metadata-standards

Metadata structure

OpenSea supports metadata that is structured according to the official ERC721 metadata standard or the Enjin Metadata suggestions.

References

• https://github.com/OpenZeppelin/openzeppelin-contracts/tree/master/contracts/token/ERC721
• https://github.com/OpenZeppelin/openzeppelin-contracts/tree/master/contracts/token/ERC1155
• https://docs.openzeppelin.com/contracts/4.x/api/token/erc721