From 3729381850ca0e41a53155d5d25cdb6dd9f91fe2 Mon Sep 17 00:00:00 2001 From: Ana Loznianu Date: Mon, 5 Jun 2023 20:11:37 +0000 Subject: [PATCH] GITBOOK-416: change request with no subject merged in GitBook --- developers/contracts/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/contracts/README.md b/developers/contracts/README.md index 51989210..cfff65f1 100644 --- a/developers/contracts/README.md +++ b/developers/contracts/README.md @@ -10,7 +10,7 @@ The V4 smart contracts have been deployed across multiple [networks](../../disco ### [**Data NFTs**](data-nfts.md) **for Enhanced Data IP Management** -In Ocean V3, the publication of a dataset involved deploying an ERC20 "datatoken" contract along with relevant metadata. This process allowed the dataset publisher to claim copyright or exclusive rights to the underlying Intellectual Property (IP). Upon obtaining 1.0 ERC20 datatokens for a particular dataset, users were granted a license to consume that dataset, utilizing the Ocean infrastructure by spending the obtained datatokens. +In Ocean V3, the publication of a dataset involved deploying an ERC20 "datatoken" contract along with relevant [metadata](metadata.md). This process allowed the dataset publisher to claim copyright or exclusive rights to the underlying Intellectual Property (IP). Upon obtaining 1.0 ERC20 datatokens for a particular dataset, users were granted a license to consume that dataset, utilizing the Ocean infrastructure by spending the obtained datatokens. However, Ocean V3 faced limitations in terms of flexibility. It lacked support for different licenses associated with the same base IP, such as 1-day versus 1-month access, and the transferability of the base IP was not possible. Additionally, the ERC20 datatoken template was hardcoded, restricting customization options.