Compare commits

...

8 Commits

Author SHA1 Message Date
Jimmy Debe
1fe438ade1 Updates 2025-12-01 22:46:29 -05:00
Jimmy Debe
6d62819cc0 Update slot-builder with fixes 2025-12-01 22:38:40 -05:00
Jimmy Debe
8ba7c3176c Updates builder.md 2025-11-28 03:53:14 -05:00
Jimmy Debe
37ff922fab Update slot-builder.md 2025-11-14 04:40:13 -05:00
Jimmy Debe
99d224b0d6 Update slot-builder.md 2025-11-14 01:12:10 -05:00
Jimmy Debe
293145cc32 Update slots 2025-11-07 01:22:05 -05:00
Jimmy Debe
b885ba66f8 slotUpdate 2025-11-06 23:13:31 -05:00
Jimmy Debe
1c91eef990 Create slot-buIlder.md 2025-08-20 11:19:27 -04:00

133
codex/raw/slot-buIlder.md Normal file
View File

@@ -0,0 +1,133 @@
---
title: CODEX-SLOT-BUILDER
name: Codex Slot Builder
status: raw
tags: codex
editor:
contributors:
- Jimmy Debe <jimmy@status.im>
---
## Abstract
This document describes the Codex slot builder mechanism.
Slots used in the Codex protocol are an important component of node collaboration in the network.
## Background
The Codex protocol places a dataset into blocks before sending a storage request to the network.
Slots control and facilitate the distribution of the data blocks to participating storage providers.
The mechanism builds individual Merkle trees for each slot, enabling cell-level proof generation, and
constructs a root verification tree over all slot roots.
## Specification
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
“SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and
“OPTIONAL” in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).
A Codex client wanting to present a dataset to the network will present a set of erasure encoded data blocks,
as described in the [CODEX-ERASURE-CODING](./erasure-coding.md) specification.
These data blocks will be placed into slots for storage providers to access.
The slot building process MUST construct a block digest Merkle tree from the data blocks.
The root hashes from this tree are used as the leaves in a slot merkle tree.
The prepared dataset is presented to storage providers in the form of slots.
A slot represents the location of a data block cell with an open storage contract.
Storage providers SHOULD be able to locate a specific data block and
all the details of the storage contract.
See, the [CODEX-MARKETPLACE](./marketplace.md) specification.
### Construct a Slot Tree
#### Block Digest Tree
A slot stores a list of root hashes that help with the retrieval of a dataset.
The block digest tree SHOULD be constructed before building any slots.
A data block is divided into cells that are hashed.
The block size MUST be divisible by the cell size for the block digest tree construction.
$$
\text{Cell size} \mid \text{Block size (in bytes)}
$$
A block digest tree SHOULD contain the unique root hashes of blocks of the entire dataset,
which MAY be based on the [Poseidon2](https://eprint.iacr.org/2023/323) algorithm.
The result of one digest tree will be represented by the root hash of the tree.
#### Slot Tree
A slot tree represents one slot,
which includes the list of digest root hashes.
If a block is empty,
the slot branch SHOULD be a hash of an empty block.
Some slots MAY be empty,
depending on the size of the dataset.
$$
\text{Blocks per slot} = \frac{\text{Total blocks}}{\text{Number of slots}}
$$
The cells per slot tree branch MUST be padded to a power of two.
This will ensure a balanced slot Merkle tree.
$$
\text{Cells per slot} = \text{Blocks per slot} \times \text{Cells per block}
$$
Below are the REQUIRED values to build a slot.
``` nim
type SlotsBuilder*[T, H] = ref object of RootObj
store: BlockStore # Storage backend for blocks
manifest: Manifest # Current dataset manifest
strategy: IndexingStrategy # Block indexing strategy
cellSize: NBytes # Size of each cell in bytes
numSlotBlocks: Natural # Blocks per slot (including padding)
slotRoots: seq[H] # Computed slot root hashes
emptyBlock: seq[byte] # Pre-allocated empty block data
verifiableTree: ?T # Optional verification tree
emptyDigestTree: T # Pre-computed empty block tree
```
### Verification Tree
Nodes within the network are REQUIRED to verify a dataset before retrieving it.
A verification tree is a Merkle proof derived from the `slotRoot`.
The entire dataset is not REQUIRED to construct the tree.
The following are the inputs to verify a proof:
```nim
type
H = array[32, byte]
Natural = uint64
type ProofInputs*[H] = object
entropy*: H # Randomness value
datasetRoot*: H # Dataset root hash
slotIndex*: Natural # Slot identifier
slotRoot*: H # Root hash of slot
nCellsPerSlot*: Natural # Cell count per slot
nSlotsPerDataSet*: Natural # Total slot count
slotProof*: seq[H] # Inclusion proof for slot in dataset
samples*: seq[Sample[H]] # Cell inclusion proofs
```
To verify, a node MUST recompute the root hash,
based on `slotProof` and the hash of the `slotIndex`,
to confirm that the `slotIndex` is a member of the dataset represented by `datasetRoot`.
## Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
## References
- [CODEX-ERASURE-CODING](./erasure-coding.md)
- [CODEX-MARKETPLACE](./marketplace.md)
- [Poseidon2](https://eprint.iacr.org/2023/323)