You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Currently, the blob module requires requesting the entire namespace data to retrieve a single blob. Because the namespace may contain multiple blobs, the client node must parse all of that data locally to find the requested blob. And also it needs to recalculate nmt proof of single blob from whole namespace proof.
This approach is inefficient and consumes unnecessary bandwidth. Instead, the blob should be transmitted directly.
NMT does not support proof recalculation. Current API returns namespace row proof instead of blob proof.
Efficient blob retrieval can be implemented using shwap, which will solve both issues. Server has capabilities to read specified blob as well as calculate blob proof, because it has access to full ODS data.
Implementation Plan:
Shwap protocol changes
Define new message types for BlobRequest and BlobResponse to enable more efficient blob transmission.
Description:
Currently, the blob module requires requesting the entire namespace data to retrieve a single blob. Because the namespace may contain multiple blobs, the client node must parse all of that data locally to find the requested blob. And also it needs to recalculate nmt proof of single blob from whole namespace proof.
Efficient blob retrieval can be implemented using shwap, which will solve both issues. Server has capabilities to read specified blob as well as calculate blob proof, because it has access to full ODS data.
Implementation Plan:
Shwap protocol changes
BlobRequest
andBlobResponse
to enable more efficient blob transmission.Accessor interface
GetBlob()
method to theAccessor
interface and all corresponding implementations.Full node adjustments
The text was updated successfully, but these errors were encountered: