Date: Tue, 19 Mar 2024 11:39:20 +0000 (UTC) Message-ID: <1194118147.55079.1710848360133@aws-us-west-2-hyp-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_55078_852678535.1710848360133" ------=_Part_55078_852678535.1710848360133 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A decentralized storage provides a singl= e source of truth for data, with unparalleled privacy, security, and transp= arency.
There are three relevant data trends.&nb= sp;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 is= sues. Three, the cloud needs to move to the edge data centers for performan= ce and availability, driven by IoT applications, multi-player gaming, = autonomous vehicles, and content streaming. Decentralization accelerates th= is change and adoption, as it lowers deployment, management, and scale-out = cost while providing better security, performance, and availability. <= /span>
The scope is to define concepts regar= ding 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, de= velopers, cloud providers, and storage system vendors in several industry v= erticals such as supply chain, healthcare, government, financial institutio= ns, real estate, insurance providers, etc
Some research topics and separation o=
f interest are:
- Generating unbiased random challenges to verify storage of data=
- Verification of data
- Execution determinism, and sources of non-determinism in existi= ng languages
- Mechanism to transact with USD or fiat currency to storage prov= iders 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 a= nd execution of agreement?
- What relationship do legal storage smart contracts have to mode= ls of computation?
- Verifiable and authenticated data structures - e.g. Merkle path= s, log-backed maps,
- How best to expose through storage smart contract languages/lib= raries
- 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 r= espected 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
= li>Proposing solutions to the problems identified
<= /li>Identifying conferences or other opportunities to c= onnect face to face
This working group will collaborate w= ith 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 alread= y expressed an interest in joining this working group, and we hope they wil= l become contributors over the first year:
Name | Company | Email Address |
---|---|---|
The following individual has voluntee= red to serve as the initial chair for the working group:
I, Saswata B= asu, am volunteering to run this group initially, unless somebody else with= interest in the group would like to volunteer.