-
Notifications
You must be signed in to change notification settings - Fork 984
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
Murisi/borsh ibc msg transfer rebase v0.41.0 #3560
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3560 +/- ##
==========================================
- Coverage 53.66% 53.36% -0.31%
==========================================
Files 322 322
Lines 111871 112422 +551
==========================================
- Hits 60037 59990 -47
- Misses 51834 52432 +598 ☔ View full report in Codecov by Sentry. |
What is the status of this @murisi? |
can we close this? @murisi |
Yeah, we can close this. But for the sake of consistency, in the future we should probably consider using Borsh (de)seralization for the IBC messages and also tagging them to bring their encoding into line with the rest of the Namada transactions. That being said, this might be more trouble than it's worth given that the hardware wallet integration of this Protobuf encoding (wrapped by a Borsh encoding) has already been implemented on the hardware wallet. |
Describe your changes
Attempt to close #3501 and hence simplify the (de)serialization of IBC transactions for third parties. More specifically, the following changes have been made:
IbcMessage
enumeration instead of being an untagged serialization of aMsgTransfer
,MsgNftTransfer
orAny
structure.Tx
are serialized using Borsh, and will ease schema generation.Indicate on which release or other PRs this topic is based on
Namada 0.41.0
Checklist before merging to
draft