Skip to content
Data Considerations for Jupiter Chain 🚀
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Architecture
DataAttributes
Operational
images
README.md

README.md

Banner https://jupiterchain.tech 🚀

Data Considerations for Jupiter Chain

This repo outlines the Jupiter Chain proposal for the storage of data in account-based blockchains for the purpose of data and consent management. Jupiter Chain use cases have three main considerations (refer to the whitepaper at https://jupiterchain.tech for more information):

  1. Identity and tracking of accounts
  2. Consent and permissioning of access to data
  3. Computation of data assessment algorithms

Goals

As such the proposed data model has the following goals:

  1. Registration of allowed owner addresses and data permissions
  2. Definition of data schema with functional relationships between data sets
  3. Storage and retrieval of data through standard data methods
  4. Optimal deployment, upgrade and removal of data set smart contracts and registry contracts without the risk of losing associated data
  5. Definition of data through a standard set of data attributes that describes the data

Requirements

The data model will have the following characteristics:

  1. Standard functions and signatures
  2. Data schema that describes the data set properties and their relationships
  3. Facilitation of data normalization and data joins
  4. A list that records owner addresses for data permission
  5. Loosely coupled data set smart contracts and registry contracts resembling a factory pattern
  6. Isolated data set smart contract and registry contract deployment

Assumptions

  1. Data Attributes and non-personal data in Ethereum based blockchains are stored onchain
  2. Personal data are stored in secure offchain storage
  3. Onchain data are stored on user addresses
  4. Files are stored offchain

Contents

Based on the Jupiter Chain use case enterprise architecture we propose a data model for the Jupiter Chain and suggest an implementation using smart contracts. The repo is organised as follows:

Contributors

  • Andrew - @andrewtud
  • Ernie - @ErnieTeo-JEDTrade
You can’t perform that action at this time.