oasisprotocol / oasisprotocol/oasis-core
Replicated storage (FEC)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Decentralized Storage epic issue for Oasis network Version E
Goals
Permissionless open network with decentralized storage servers.
Details
Storage servers contract with the network to provide storage; network infra handles data migration at end of contract period. Want greater storage efficiency (less data duplication); better fault tolerance efficiency.
Linked Issues
- Switching to FEC+CAS instead of F+1 CAS for storage efficiency, higher sybil resistance
- Storage economics -- Gas fractions to pay compute vs storage, storage contract, slashing
- Storage verification mechanism design -- what service performs probing to verify storage compliance, how to probe (uniform over all storage locations? over contracts? what frequency?)
- Storage server API changes (DoS prevention, authn/authz, storage receipt)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the linked storage verification mechanism design issue and the listed FEC+CAS, storage economics, and storage server API topics; the issue does not define a concrete implementation boundary or completion criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100