From 5cc4f42810267da9ba4cc47c8eb8cbbe990cd89c Mon Sep 17 00:00:00 2001 From: Akshay Date: Wed, 25 May 2022 17:41:34 +0200 Subject: [PATCH] Issue-#960: Update permissions.md and architecture.md --- content/concepts/architecture.md | 4 ++-- content/tutorials/permissions.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/concepts/architecture.md b/content/concepts/architecture.md index 0e45efac..b2cc7ae8 100644 --- a/content/concepts/architecture.md +++ b/content/concepts/architecture.md @@ -23,13 +23,13 @@ Here’s an overview of the figure. Data NFTs are based on [ERC721](https://eips.ethereum.org/EIPS/eip-721) standard. The publisher can use Marketplace or client libraries to deploy a new data NFT contract. To save gas fees, it uses [ERC1167](https://eips.ethereum.org/EIPS/eip-1167) proxy approach on the **ERC721 template**. Publisher can then assign manager role to other Ethereum addresses who can deploy new datatoken contracts and even mint them. Each datatoken contract is associated with one data NFT contract. Click [here](/concepts/datanft-and-datatoken/) to further read about data NFTs and datatokens. -ERC721 data NFTs represent holding copyright/base IP of a data asset, and ERC20 datatokens represent licenses to access the asset by downloading the content or running Compute-to-data job. +ERC721 data NFTs represent holding copyright/base IP of a data asset, and ERC20 datatokens represent licenses to access the asset by downloading the content or running Compute-to-Data jobs. Datatoken represents the asset that the publisher wants to monetize. The asset can be a dataset or an algorithm. The publisher actor holds the asset in Google Drive, Dropbox, AWS S3, on their phone, on their home server, etc. The publisher can optionally use IPFS for a content-addressable URL. Or instead of a file, the publisher may run a compute-to-data service. In the **publish** step, the publisher invokes **Ocean Datatoken Factory** to deploy a new datatoken to the chain. To save gas fees, it uses [ERC1167](https://eips.ethereum.org/EIPS/eip-1167) proxy approach on the **ERC20 datatoken template**. The publisher then mints datatokens. -The publisher runs their own **Ocean Provider** or can use one deployed by Ocean Protocol. In the **download** step or while running C2D job, Provider software needs to retrieve the data service URL given a datatoken address. One approach would be for the publisher to run a database. However, this adds another dependency. To avoid this, the Provider encrypts the URL and this encrpyted URL gets published on-chain. +The publisher runs their own **Ocean Provider** or can use one deployed by Ocean Protocol. In the **download** step or while running C2D job, Provider software needs to retrieve the data service URL given a datatoken address. One approach would be for the publisher to run a database. However, this adds another dependency. To avoid this, the Provider encrypts the URL, which then gets published on-chain. To initiate the **download** step, the data buyer sends 1.0 datatokens to the Provider wallet. Then they make a service request to the Provider. The Provider loads the encrypted URL, decrypts it, and provisions the requested service (send static data, or enable a compute-to-data job). diff --git a/content/tutorials/permissions.md b/content/tutorials/permissions.md index 1dde2b88..902b1126 100644 --- a/content/tutorials/permissions.md +++ b/content/tutorials/permissions.md @@ -1,6 +1,6 @@ --- title: Fine-Grained Permissions -description: Control who can publish, download or browse data +description: Control who can publish, buy or browse data ---