A decentralized storage provides a single source of truth for data, with unparalleled privacy, security, and transparency.
There are three relevant data trends. One, data is expected to grow from 33 ZB (zettabytes) today to 175 ZB in 5 years. Two, data breaches are a growing problem with $150M+ liability issues. Three, the cloud needs to move to the edge data centers for performance and availability, driven by IoT applications, multi-player gaming, autonomous vehicles, and content streaming. Decentralization accelerates this change and adoption, as it lowers deployment, management, and scale-out cost while providing better security, performance, and availability.
The scope is to define concepts regarding decentralized storage and to produce material to describe the various aspects and meanings, trying to come up to standards or good practices. The audience for decentralized storage is large and spans from researchers, developers, cloud providers, and storage system vendors in several industry verticals such as supply chain, healthcare, government, financial institutions, real estate, insurance providers, etc
Some research topics and separation of interest are:
- Generating unbiased random challenges to verify storage of data
- Verification of data
- Execution determinism, and sources of non-determinism in existing languages
- Mechanism to transact with USD or fiat currency to storage providers and clients
- Cost models for metering challenges and verification
- Paradigms for storage provider selection - e.g. based on region, challenge response time, price, public reputation via oracle
- Parallelism of execution, state independence
- What properties should storage smart contracts with 'SLA' have?
- At what scale to smart contracts best contribute to certainty and execution of agreement?
- What relationship do legal storage smart contracts have to models of computation?
- Verifiable and authenticated data structures - e.g. Merkle paths, log-backed maps,
- How best to expose through storage smart contract languages/libraries
- Sharing state back-ends across execution engines
- Conflict-free and additive data structures
- Multi-party secure share of data
- Proxy re-encryption
- Zero knowledge
The anticipated initial work products will include (but is not limited to):
White Paper about storage smart contracts and the respected aspects concerning their development, deployment and usage
Identifying use cases, case studies
Produce 'Requests To Build' that could feed into feature planning on the different Hyperledger frameworks
Exploring security, privacy, legal boundaries
Proposing solutions to the problems identified
Identifying conferences or other opportunities to connect face to face
This working group will collaborate with other Hyperledger working groups, the TSC, Linux Foundation staff, and the project maintainers. Especially the following Working Groups and their subgroups will be of great importance in achieving the anticipated results.
The following individuals have already expressed an interest in joining this working group, and we hope they will become contributors over the first year:
List of interested parties (listed with their consent), including name, association, and optionally email addresses.
The following individual has volunteered to serve as the initial chair for the working group:
I, Saswata Basu, am volunteering to run this group initially, unless somebody else with interest in the group would like to volunteer.