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
I would like to propose some improvements to the documentation found in the eigenda/inabox README regarding the gRPC commands for sending and retrieving blob status.
Suggested Changes:
Update the command for dispersing a blob:
Current command:
Reason: This change captures the REQUEST_ID directly in the command, making it easier for users to reference this ID in subsequent commands without needing to manually extract it.
Update the command for checking blob status:
Current command:
Reason: Using double quotes for the JSON string allows for proper variable interpolation, ensuring that the value of REQUEST_ID is correctly passed in the request.
Additional information.
Thank you for considering these changes!
The text was updated successfully, but these errors were encountered:
@l0g2 very much agree with you here, I had the same hiccups when first playing with these. May I suggest you put a quick PR up for this, I'll gladly accept it.
Documentation.
I would like to propose some improvements to the documentation found in the eigenda/inabox README regarding the gRPC commands for sending and retrieving blob status.
Suggested Changes:
Update the command for dispersing a blob:
Current command:
Suggested command:
Reason: This change captures the
REQUEST_ID
directly in the command, making it easier for users to reference this ID in subsequent commands without needing to manually extract it.Update the command for checking blob status:
Current command:
grpcurl -plaintext -d '{"request_id": "$REQUEST_ID"}' \ localhost:32003 disperser.Disperser/GetBlobStatus
Suggested command:
grpcurl -plaintext -d "{\"request_id\": \"$REQUEST_ID\"}" \ localhost:32003 disperser.Disperser/GetBlobStatus
Reason: Using double quotes for the JSON string allows for proper variable interpolation, ensuring that the value of
REQUEST_ID
is correctly passed in the request.Additional information.
Thank you for considering these changes!
The text was updated successfully, but these errors were encountered: