The existing CellPtr is constrained to addressing a maximum of 2^23 (or 8,388,608) cells, which is proving to be insufficient. The limitation does not stem from the CellPtr itself, which is currently a u32, but rather from the Cell, which is a u64 and must contain two TermPtr's in addition to a reference to the symbol, polarity, and other elements.
To address this limitation, we may need to consider reducing some metadata from cells and opting for a lookup approach instead. This issue aims to explore and develop strategies to enhance the addressing capacity of CellPtr by optimizing the storage and retrieval of cell-related metadata, ensuring that the system can manage a larger number of cells efficiently and effectively.
The existing
CellPtris constrained to addressing a maximum of 2^23 (or 8,388,608) cells, which is proving to be insufficient. The limitation does not stem from theCellPtritself, which is currently a u32, but rather from theCell, which is a u64 and must contain twoTermPtr'sin addition to a reference to the symbol, polarity, and other elements.To address this limitation, we may need to consider reducing some metadata from cells and opting for a lookup approach instead. This issue aims to explore and develop strategies to enhance the addressing capacity of
CellPtrby optimizing the storage and retrieval of cell-related metadata, ensuring that the system can manage a larger number of cells efficiently and effectively.