codex-storage
/
codex.storage
mirror of https://github.com/codex-storage/codex.storage.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

chore: update content

This commit is contained in:
jinhojang6 2023-10-04 18:38:34 +09:00
parent 7d1ec6f142
commit ba67fa245c
2 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
about/architect.md
View File

@ -42,15 +42,15 @@ Codex is composed of multiple node types, each taking a different role in the ne
As Codex's long-term reliable storage providers, storage nodes stake collateral based on the collateral posted on the request side of contracts, and the number of slots that a contract has. This is tied to the durability demanded by the user. Failure to provide periodic proof of data possession results in slashing penalties.
**Caching nodes**
**Aggregator**
Anyone can contribute to Codex as an ephemeral node by caching and serving popular content without requiring reliable or abundant storage. These caching nodes act to scale the network during periods of high demand.
A method for off-loading erasure coding and proof generation and proof aggregation by a client node with low-resources, currently a WIP and will be part of subsequent Codex release Q2/Q4 next year.
**Client nodes**
Client nodes make requests for other nodes to store, find, and retrieve data. Most of the Codex network will be Client nodes, and these participants can double as caching nodes to offset the cost of the network resources they consume.
When a node commits to a storage contract and a user uploads data, the network will proactively verify that the storage node is online and that the data is retrievable. Storage nodes then broadcast proofs of data possession over random intervals.
When a node commits to a storage contract and a user uploads data, the network will proactively verify that the storage node is online and that the data is retrievable. Storage nodes are then randomly queried to broadcast proofs of data possession over an interval corresponding to the contract duration and 9's of retrievability guarantee the protocol provides.
If the storage node sends invalid proofs or fails to provide them in time, the network evicts the storage node from the slot, and the slot will become available for the first node that generates a valid proof for that slot.

2
about/roadmap.md
View File

@ -12,8 +12,6 @@ Codex is currently in its first proof of concept iteration, codenamed Dagger. Be
- **Scimitar:** The PoC-2 client will implement fast erasure coding, the marketplace, and partial durability guarantees—expected end of Q3 2023.
- **Longsword:** Codex PoC-3 will improve upon SNARK-based remote auditing mechanism and add bandwidth incentives to the marketplace—expected end of Q3 2023.
- **Katana:** Codex v1 will offer SNARK-based remote auditing
<br/>