oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

Improve v4 docs

Browse Source
This commit is contained in:
Akshay 2021-08-17 12:24:01 +02:00
parent 0ebca72187
commit 6baece929b
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
content/concepts/images/v4-nft-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 16 KiB

4
content/concepts/v4-nft.md
View File

@ -10,13 +10,15 @@ 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.
![Image 1](images/v4-nft-1.png)
### 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)
![Combining ERC721 and ERC20](images/v4-nft-2.png)
Once the contract is deployed, it will be available on the Ocean Marketplace for trade.