logos-storage/logos-storage-spec
1
0
Fork 0
mirror of https://github.com/logos-storage/logos-storage-spec.git synced 2026-01-08 00:13:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Create erasue-coding.md

Browse Source
This commit is contained in:
Jimmy Debe 2024-09-19 22:57:21 -04:00 committed by GitHub
parent 3a3e4d09f1
commit ea804e84d1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 42 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
specs/erasue-coding.md Normal file
View File

@ -0,0 +1,42 @@
---
title: CODEX-ERASUE-CODING
name: Codex Erasue Coding
status: raw
tags: codex
editor:
contributors:
---
## Abstract
This specification describes the erasue coding technique used in the Codex protocol.
Erasue coding is used by the Codex client to encode datasets being presented to the [marketplace]().
## Background
Codex uses storage proofs to determine whether a storage provider is storing a certain dataset.
Storage providers agree to store dataset for a period of time and
store an encoded dataset provded by the requester.
Using erasure coding,
client nodes will be able to restore datasets thatare abandoned by storage providers.
Also validator nodes are able to detect whether data is missing within a slot.
## Semantics
The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”,
“SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and
“OPTIONAL” in this document are to be interpreted as described in [2119](https://www.ietf.org/rfc/rfc2119.txt).
The Codex client performerasure coding locally before provding dataset to the marketplace.
### Flow
Before data is provided to storage providers on the marketplace,
clients must do the following:
1.
## Security Considerations