From 0ebca7218783f32631a116648213d932461daaa2 Mon Sep 17 00:00:00 2001 From: Akshay Date: Tue, 17 Aug 2021 12:11:30 +0200 Subject: [PATCH] Improve v4 docs --- content/concepts/v4-nft.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/concepts/v4-nft.md b/content/concepts/v4-nft.md index 1899e731..681cf482 100644 --- a/content/concepts/v4-nft.md +++ b/content/concepts/v4-nft.md @@ -10,6 +10,12 @@ A non-fungible token stored on the blockchain represents a unique asset. NFTs ca Ocean Protocol defines an [ERC721Factory](https://github.com/oceanprotocol/contracts/blob/v4Hardhat/contracts/ERC721Factory.sol) contract which will allow users to deploy ERC721 contract instances on any of the supported networks. The deployed contract can be associated with Metadata information which describes, also published on-chain. The [Metadata](https://github.com/oceanprotocol/contracts/blob/v4Hardhat/contracts/metadata/Metadata.sol) contract will store the information about the asset, and associated access rights defined through roles. +### Combining ERC721 and ERC20 + +ERC20 interface represents fungible tokens. ERC721 and ERC20 combined together can be used for sub-licensing. These sub-licenses can be traded on any AMM as the underlying contract is ERC20 compliant. + +Ocean Protocol's [ERC721Template](https://github.com/oceanprotocol/contracts/blob/v4Hardhat/contracts/templates/ERC721Template.sol) provides functionality to create comibinations of ERC721 and ERC20 contract pairs, each of this pair can represent a different sub-license. + ![Image 1](images/v4-nft-1.png) Once the contract is deployed, it will be available on the Ocean Marketplace for trade.