docs/content/concepts/v4-nft.md

38 lines
3.1 KiB
Markdown
Raw Normal View History

2021-09-28 11:49:24 +02:00
### NFTS
2021-09-28 11:49:24 +02:00
A non-fungible token stored on the blockchain represents a unique asset. NFTs can represent images, videos, digital art, or any piece of information. NFTs can be traded and allow transfer of ownership and copyright. [EIP-721](https://eips.ethereum.org/EIPS/eip-721) defines an interface for handling NFTs on Ethereum blockchain. The creator of the NFT can deploy a new contract on Ethereum or any Blockchain supporting NFT related interface and also, transfer the ownership through the transaction(s).
2021-09-28 11:49:24 +02:00
### Terminology
2021-09-28 11:49:24 +02:00
- **Base IP** means the artifact being copyrighted. Represented by the {ERC721 address, tokenId} from the publish transactions.
2021-09-28 11:49:24 +02:00
- **Base IP holder** means the holder of the Base IP. Represented as the the actor that did the initial "publish" action.
2021-09-28 11:49:24 +02:00
- **Sub-licensee** is the holder of the sub-license. Represented as the entity that controls address ERC721.\_owners[tokenId=x].
2021-09-28 11:49:24 +02:00
- **To Publish**: Claim copyright or exclusive base license
2021-08-17 12:24:01 +02:00
2021-09-28 11:49:24 +02:00
- **To Sub-license**:Transfer one (of many) sub-licenses to new licensee: ERC20.transfer(to=licensee, value=1.0)
2021-08-17 12:11:30 +02:00
2021-09-28 11:49:24 +02:00
### Supporting NFT using Ocean Protocol
2021-08-17 12:11:30 +02:00
2021-09-28 11:58:15 +02:00
Ocean Protocol defines [ERC721Factory](https://github.com/oceanprotocol/contracts/blob/v4main/contracts/ERC721Factory.sol) contract, allowing **Base IP holders** to create their ERC721 contract instances on any supported networks. The deployed contract stores Metadata, ownership, sub-license information, permissions. The creator of the contract can also create and mint ERC20 token instances for sub-licensing the **Base IP**.
2021-08-17 12:11:30 +02:00
2021-09-28 11:49:24 +02:00
### Sub licensing the Base IP
2021-09-28 11:58:15 +02:00
ERC721 tokens are non-fungible, thus cannot be used for automatic price discovery like ERC20 tokens. ERC721 and ERC20 combined together can be used for sub-licensing. Ocean Protocol's [ERC721Template](https://github.com/oceanprotocol/contracts/blob/v4main/contracts/templates/ERC721Template.sol) solves this problem by using ERC721 for tokenizing the **Base IP** and tokenizing sub-licenses by using ERC20. Thus, sub-licenses can be traded on any AMM as the underlying contract is ERC20 compliant.
2021-09-28 11:49:24 +02:00
### Use case
2021-09-28 11:58:15 +02:00
Alice is the author of a book. Alice wants to hold the copyright of her work but, allows others to read her book. So, She creates 2 versions of her book namely: digital copy, physical copy. She assigns Bob as one of the holder of digital edition of the book. Here, **Base IP** is the book. **Base IP holder** is Alice and Bob is **Sub-licensee** for a digital edition of the book. Alice tokenizes her work by performing **Publish** action i.e _ERC721.safeMint(to=aliceWalletAddress, tokenid=1)_. Alice also creates sub-licenses of her book by creating two ERC20 tokens and transefers the digital copy token to Bob's wallet.
2021-09-28 11:49:24 +02:00
![Image 1](images/v4-nft-1.PNG)
### Other References
- https://en.wikipedia.org/wiki/Non-fungible_token
- https://blog.oceanprotocol.com/nfts-ip-1-practical-connections-of-erc721-with-intellectual-property-dc216aaf005d
2021-09-28 11:49:24 +02:00
- https://blog.oceanprotocol.com/nfts-ip-2-leveraging-erc20-fungibility-bcee162290e3
- https://blog.oceanprotocol.com/nfts-ip-3-combining-erc721-erc20-b69ea659115e
- https://blog.oceanprotocol.com/on-difficult-to-explain-fungibility-sightings-in-nfts-26bc18620f70