MallCloud / contracts-api

API for communicating with Ethereum Contracts
0 stars 0 forks source link

IPFS based storage for various metadata #21

Closed kgupta15 closed 6 years ago

kgupta15 commented 6 years ago

Use IPFS for creating metadata for various transactions and functions in the c-api.

How it will work

IPFS acts exactly like a regular database, but it has a size limit and it supports blockchain. So, it can be used as a memory for metadata which is too big for a contract. For each contract that has too much metadata, an IPFS url will be created that points to location where this metadata is stored. This URL will be stored in contract so that it is accessible.

Important: IPFS is encrypted but still not proven secure. So, no confidential information like passwords etc, should be stored until its provably secure by IPFS team.

What contracts will be using IPFS

Datasets will mention their fields in the IPFS storage. If someone wishes to buy only partial dataset, they can do so by picking the fields from IPFS.

Collaboration details that are not related to transactions based on money yet, like sharing dataset or algorithm with a peer, can be done using IPFS. IPFS will store basic information of all users that are involved in sharing of any Analytic Object.

Data in Contracts Contracts will hold data that should be uneditable. Examples :

  1. Notebook : DIN
  2. DataSet : DIN
  3. RFS : DIN of all notebooks and datasets.

Data in IPFS IPFS will hold data that will be editable and will be changed many times. Examples :

  1. Notebook : Details of algorithm
  2. Dataset : Fields/Parameters
  3. RFS : Details/Fields of Notebook/Dataset
kgupta15 commented 6 years ago

Completed.