a minor fix on the namespace id size calculation

celestiaorg · Mar 6, 2023 · 93a70ae · 93a70ae
1 parent 7686701
commit 93a70ae
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/spec/nmt-wrapper.md b/docs/spec/nmt-wrapper.md
@@ -51,7 +51,7 @@ Thus, the namespace ID of a share in `Q0` can be extracted from the first `Names
 However, shares in `Q1`, `Q2`, and `Q3` (that are erasure-coded versions of `Q0` and known as parity shares) do not have any namespace IDs by default. 
 These shares must be assigned a reserved namespace ID, which is called `ParitySharesNamespaceID`.
 The `ParitySharesNamespaceID` corresponds to the lexicographically last namespace ID that can be represented by `NamespaceIDSize` bytes.
-"If `NamespaceIDSize` is `8`, then the value of `ParitySharesNamespaceID` is `2^8-1`, which is equivalent to `0xFFFFFFFFFFFFFFFF`.
+"If `NamespaceIDSize` is `8`, then the value of `ParitySharesNamespaceID` is `2^64-1`, which is equivalent to `0xFFFFFFFFFFFFFFFF`.
 In Celestia, the values for `NamespaceIDSize` and `ParitySharesNamespaceID` can be found in [`NAMESPACE_ID_BYTES`](https://github.com/celestiaorg/celestia-app/blob/specs-staging/specs/src/specs/consensus.md#constants) constant and the [`PARITY_SHARE_NAMESPACE_ID`](https://github.com/celestiaorg/celestia-app/blob/specs-staging/specs/src/specs/consensus.md#reserved-namespace-ids), respectively.
 
 ### NMT Wrapper Data Insertion