From 12a4f8c43469b4f1257c959c5b0e2b8eeb68a561 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Tue, 24 Sep 2024 22:36:47 -0400
Subject: [PATCH] Update erasue-coding.md

---
 specs/erasue-coding.md | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/specs/erasue-coding.md b/specs/erasue-coding.md
index 8e5e6d9..2074819 100644
--- a/specs/erasue-coding.md
+++ b/specs/erasue-coding.md
@@ -34,8 +34,28 @@ The Codex client performerasure coding locally before provding dataset to the ma
 Before data is provided to storage providers on the marketplace,
 clients must do the following:
 
-1.  
+1.  Create data chunks from the data
+2.  Encode each chunk with Reed Solomon erasue coding, more explained below
+3.  Derive an CID from encoded chunks share on the marketplace
+4.  Error correction by validator nodes once storage contract begins
 
+ 
+### Create Data chunks
+
+After the user has choosen the prefered data for storage through the marketplace,
+the Codex client will divide this data into chunks , e.g. 
+Including the [manifest](manifest), the data chucks will be encoded based on the following parameters:
+
+```js
+struct encodingParms {
+  ecK: int
+  ecM: int
+  rounded: int
+  steps: int
+  blocksCount: int
+  strategy: 
+}
+```
 
 
 ## Security Considerations