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

GITBOOK-415: change request with no subject merged in GitBook

Browse Source
This commit is contained in:
Ana Loznianu 2023-06-05 20:10:15 +00:00 committed by gitbook-bot
parent 9724a9e0c8
commit ec2d5a8345
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
4 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
developers/contracts/README.md
View File

@ -16,7 +16,7 @@ However, Ocean V3 faced limitations in terms of flexibility. It lacked support f
Ocean V4 effectively tackles these challenges by adopting **ERC721** **tokens** to explicitly represent the **base IP** as "data NFTs" (Non-Fungible Tokens). [**Data NFT**](data-nfts.md) owners can now deploy ERC20 "datatoken" contracts specific to their data NFTs, with each datatoken contract offering its own distinct licensing terms. Ocean V4 effectively tackles these challenges by adopting **ERC721** **tokens** to explicitly represent the **base IP** as "data NFTs" (Non-Fungible Tokens). [**Data NFT**](data-nfts.md) owners can now deploy ERC20 "datatoken" contracts specific to their data NFTs, with each datatoken contract offering its own distinct licensing terms.
By utilizing ERC721 tokens, Ocean V4 grants data creators greater flexibility and control over licensing arrangements. The introduction of data NFTs allows for the representation of base IP and the creation of customized ERC20 datatoken contracts tailored to individual licensing requirements.  By utilizing ERC721 tokens, Ocean V4 **grants data creators greater flexibility and control over licensing arrangements**. The introduction of data NFTs allows for the representation of [base IP](../../discover/glossary.md#base-ip) and the creation of customized ERC20 datatoken contracts tailored to individual licensing requirements. 
@ -46,4 +46,4 @@ Key features of the V4 smart contracts:
* Multiple NFT template support: the Factory can deploy different types of NFT templates 🖼️ * Multiple NFT template support: the Factory can deploy different types of NFT templates 🖼️
* Multiple datatoken template support: the Factory can deploy different types of [datatoken templates](datatoken-templates.md). * Multiple datatoken template support: the Factory can deploy different types of [datatoken templates](datatoken-templates.md).
In the forthcoming pages, you will discover comprehensive information about the key features. If you have any inquiries or find anything missing, feel free to contact the core team on [Discord](https://discord.com/invite/TnXjkR5) 💬 In the forthcoming pages, you will discover more information about the key features. If you have any inquiries or find anything missing, feel free to contact the core team on [Discord](https://discord.com/invite/TnXjkR5) 💬

2
developers/contracts/community-monetization.md
View File

@ -1,5 +1,7 @@
# Community monetization # Community monetization
\------WORK in PROGRESS------
**Ocean V4 provides more upside for marketplace operators, and makes space for a market of third-party Providers.** **Ocean V4 provides more upside for marketplace operators, and makes space for a market of third-party Providers.**
Ocean V3 smart contracts enabled marketplace operators to collect a fee in just one place: consume. The value was hardcoded to 0.1% which was a good start, but it limited the upside. Ocean V3 smart contracts enabled marketplace operators to collect a fee in just one place: consume. The value was hardcoded to 0.1% which was a good start, but it limited the upside.

2
developers/contracts/datanft-and-datatoken.md
View File

@ -23,7 +23,7 @@ For a more comprehensive exploration of intellectual property and its practical
{% embed url="https://blog.oceanprotocol.com/nfts-ip-1-practical-connections-of-erc721-with-intellectual-property-dc216aaf005d" %} {% embed url="https://blog.oceanprotocol.com/nfts-ip-1-practical-connections-of-erc721-with-intellectual-property-dc216aaf005d" %}
**Details of implementation:** **DataNFTs and Datatokens example:**
* In step 1, Alice **publishes** her dataset with Ocean: this means deploying an ERC721 data NFT contract (claiming copyright/base IP), then an ERC20 datatoken contract (license against base IP). * In step 1, Alice **publishes** her dataset with Ocean: this means deploying an ERC721 data NFT contract (claiming copyright/base IP), then an ERC20 datatoken contract (license against base IP).
* In step 2, she **mints** some ERC20 datatokens and **transfers** 1.0 of them to Bob's wallet; now he has a license to be able to download that dataset. * In step 2, she **mints** some ERC20 datatokens and **transfers** 1.0 of them to Bob's wallet; now he has a license to be able to download that dataset.

2
developers/contracts/datatokens.md
View File

@ -16,7 +16,7 @@ By using datatokens, data owners can retain ownership and control over their dat
### Understanding Datatokens and Licenses ### Understanding Datatokens and Licenses
Each datatoken represents a **sub-license** from the base intellectual property (IP) owner, enabling users to access and consume the associated dataset. The license terms can be set by the data NFT owner or default to a predefined "good default" license. The fungible nature of ERC20 tokens aligns perfectly with the fungibility of licenses, facilitating seamless exchangeability and interoperability between different datatokens. Each datatoken represents a [**sub-license**](../../discover/glossary.md#sub-licensee) from the base intellectual property (IP) owner, enabling users to access and consume the associated dataset. The license terms can be set by the data NFT owner or default to a predefined "good default" license. The fungible nature of ERC20 tokens aligns perfectly with the fungibility of licenses, facilitating seamless exchangeability and interoperability between different datatokens.
By adopting the ERC20 standard for datatokens, Ocean Protocol ensures compatibility and interoperability with a wide array of ERC20-based wallets, [decentralized exchanges (DEXes)](https://blog.oceanprotocol.com/ocean-datatokens-will-be-tradeable-on-decentrs-dex-41715a166a1f), decentralized autonomous organizations (DAOs), and other blockchain-based platforms. This standardized approach enables users to effortlessly transfer, purchase, exchange, or receive datatokens through various means such as marketplaces, exchanges, or airdrops. By adopting the ERC20 standard for datatokens, Ocean Protocol ensures compatibility and interoperability with a wide array of ERC20-based wallets, [decentralized exchanges (DEXes)](https://blog.oceanprotocol.com/ocean-datatokens-will-be-tradeable-on-decentrs-dex-41715a166a1f), decentralized autonomous organizations (DAOs), and other blockchain-based platforms. This standardized approach enables users to effortlessly transfer, purchase, exchange, or receive datatokens through various means such as marketplaces, exchanges, or airdrops.