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
Similarly for PutBlob
Currently, the name is misleading. Because blob contains other metadata prepended to the user data.
In more details, eigenda_client does the following
rollup data
create a blob header containing rollup data length
do a codec on the (header || rollup date) by padding an empty byte for every 31 bytes.
to commit the polynomial, we have to pad the above data to next power of 2. Because if we want to open a point later, so it has to be the next power of 2. For most fraud proof use case, we treat the the processed data above as evaluation of a polynomial (if the data is not fault provable, it restriction can be removed)
Because of the step 2, GetBlob is incorrect, similarly PutBlob in incorrect.
Enhancement
Change the interface into PutUserData, GetUserData
Solution proposal
as above
Additional Information
No response
The text was updated successfully, but these errors were encountered:
EigenDA can servers non-rollup users, making it more generic.
or clientData
samlaf
changed the title
[Enhancement]: Rename api.clients.eigenda_client.IEigenDAClient.GetBlob as GetUserData
[Enhancement]: Rename api.clients.eigenda_client.IEigenDAClient.GetBlob as GetPayload
Jan 10, 2025
Use case and current behavior
Similarly for PutBlob
Currently, the name is misleading. Because blob contains other metadata prepended to the user data.
In more details, eigenda_client does the following
Because of the step 2, GetBlob is incorrect, similarly PutBlob in incorrect.
Enhancement
Change the interface into PutUserData, GetUserData
Solution proposal
as above
Additional Information
No response
The text was updated successfully, but these errors were encountered: