-
Notifications
You must be signed in to change notification settings - Fork 972
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Proofs are serialized as strings - undocumented API break in 0.13.0 #3173
Comments
You can see the difference in |
I've just noticed that this also is inconsistent with other rpc methods, like |
@zvolin yes i don't think this was intentional, let me chase and discuss with team and i think we'll have to change |
@renaynay here is the culprit 625cdf3#diff-e0265c8a8ef591c5dac3ccd849803c7c79932ed3b87bff256fdf9f291611ace4R38 i believe we just need to remove this custom Marshall/Unmarshal and we'll be back to original behavior |
yup, all our tests passes on that |
Perfect |
…celestiaorg#3204) Reverts a change introduced in celestiaorg#3146 that unintentionally broke `blob.Proof` serialisation. Resolves celestiaorg#3173
…celestiaorg#3204) Reverts a change introduced in celestiaorg#3146 that unintentionally broke `blob.Proof` serialisation. Resolves celestiaorg#3173
Celestia Node version
0.13.0
OS
archlinux
Install tools
No response
Others
No response
Steps to reproduce it
In #3146 change, the Proof serialization changed from a list of proof objects to the list of stringified objects. This is a breaking change for the RPC clients. Is this new behavior expected and should clients like rust celestia-rpc align to it?
My 2 cents is that previous API is cleaner, the string serialization seems rather unnecessary
Expected result
.
Actual result
.
Relevant log output
No response
Notes
No response
The text was updated successfully, but these errors were encountered: