FAQ

How is the ChiaGods method of storing data on the blockchain better than previous NFT collections that stored base64 data URIs directly in the NFTs?

In earlier NFT projects, image data was often embedded directly into the NFTs as base64 Data URIs. This approach meant that every time the NFT was moved on the blockchain, the image data had to be included in the transaction. Depending on the image size, this consumed a significant portion of block space. As Chia continues to grow and blockchain activity increases, this method would lead to higher transaction fees and make transferring NFTs increasingly expensive and inefficient over time.

ChiaGods takes a more efficient approach by chunking the NFT data and storing it in separate coins, distinct from the NFT coins themselves. The NFT contains references and lineage to these data coins, allowing it to remain lightweight. This ensures that the data is permanently stored in the blockchain’s history without needing to be duplicated in future transactions. As a result, transferring ChiaGods NFTs incurs minimal transaction fees, making them as lightweight as any other NFT on the Chia Blockchain while still retaining full data integrity.

How is the image data actually represented in the memo field? Isn’t the memo field a text field?

While the memo field may appear as a text field in most popular wallet software, it is actually a raw bytes field on the blockchain. This allowed us to store the image data directly in its raw byte format when chunking it, rather than converting it to hex or another textual representation. By doing so, we kept the memos compact, efficient, and easy to reconstruct back into complete image files. This approach ensures both optimal storage and seamless data retrieval.