This post is a Vac RFC discussion for the CODEX-MARKETPLACE RFC. The goal of RFC discussions is to discuss early RFCs that are under active development. Similar to the IETF, which has working groups who handle RFC drafts by reviewing and encouraging open discussion through mailing lists or IETF meetings. Contributors are open to discuss potential future protocol additions, security considerations and other feedback.
The Codex network uses a smart contract marketplace mechanism to create a peer-to-peer decentralized storage solution. The marketplace allows clients to request storage of data with specific parameters, facilitates storage providers (SPs) to store a portion of the data if the parameters are favorable, and allows validators to enforce that SPs provide storage proofs when challenged. The CODEX-MARKETPLACE RFC describes the components associated with each Codex node role.
Key Components:
- Storage Request Lifecycle
- Storage Provider and Validator Incentives
- Storage Proofs
- Data Repairs
Why is the marketplace is important?
Codex is a decentralized data storage protocol with censorship resistance and durability guarantees. To be a useful decentralized alternative to centralized storage, the marketplace must provide key features. The dispersal of data to be stored within the network. Incentives for good storage behavior including penalties for storage providers not providing storage proofs. The CODEX-MARKETPLACE aims to maintain the integrity, redundancy and availability of data while stored on the network.
Get Involved
- Review the CODEX-MARKETPLACE specification.
- The reference implementation is located here.