From ea804e84d1d90f225582319697bfbc861a458825 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Thu, 19 Sep 2024 22:57:21 -0400
Subject: [PATCH] Create erasue-coding.md

---
 specs/erasue-coding.md | 42 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 specs/erasue-coding.md

diff --git a/specs/erasue-coding.md b/specs/erasue-coding.md
new file mode 100644
index 0000000..8e5e6d9
--- /dev/null
+++ b/specs/erasue-coding.md
@@ -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
+