mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
f24d95a5a7
* Creating new page structure in developers section * Updating navigation * Splitting up DDO page and putting examples within details sections * Updated navigation * Updating table * GITBOOK-1: change request with no subject merged in GitBook * GITBOOK-2: change request with no subject merged in GitBook * Updating tables * Fixing services table * Updating tables * Updating algorithm page * Updating compute to data page * Updating API section * Adding the fine-grained permissions page * Adding Market-Level Permissions page * updating navigation * Updating fine grained permissions * adding information on DIDs * Updating navigation * Updating did and ddo page * GITBOOK-5: Adding video
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
---
|
|
title: Compute-to-Data
|
|
description: Datasets and Algorithms
|
|
---
|
|
|
|
# Datasets & Algorithms
|
|
|
|
### Datasets & Algorithms
|
|
|
|
With Compute-to-Data, datasets are not allowed to leave the premises of the data holder, only algorithms can be permitted to run on them under certain conditions within an isolated and secure environment. Algorithms are an asset type just like datasets and can be priced in the same way.
|
|
|
|
Algorithms can be public or private by setting `"attributes.main.type"` value in DDO as follows:
|
|
|
|
* `"access"` - public. The algorithm can be downloaded, given appropriate datatoken.
|
|
* `"compute"` - private. The algorithm is only available to use as part of a compute job without any way to download it. The Algorithm must be published on the same Ocean Provider as the dataset it's targeted to run on.
|
|
|
|
For each dataset, publishers can choose to allow various permission levels for algorithms to run:
|
|
|
|
* allow selected algorithms, referenced by their DID
|
|
* allow all algorithms published within a network or marketplace
|
|
* allow raw algorithms, for advanced use cases circumventing algorithm as an asset type, but most prone to data escape
|
|
|
|
All implementations should set permissions to private by default: upon publishing a compute dataset, no algorithms should be allowed to run on it. This is to prevent data escape by a rogue algorithm being written in a way to extract all data from a dataset.
|