-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add serialization and deserialization features for codec and borsh to the host type in ics24 #259
Comments
I encountered some problems when implementing the |
I don't really understand the issue you're describing here. Could you provide some relevant links (e.g. link to the macro you're referring to), and perhaps rephrase as well? |
This might not be the best place for this discussion, but I had previously tried serializing via borsh (by forking ibc-rs to add Around this time, I realized that most of IBC already had protobuf serializations so it was a lot easier to commit to protobuf representation for serialization/deserialization. Maybe some guidance around using |
yet, This error message is a good illustration of what I mean |
Hey man do you have any idea, not only borsh but also codec is like this, can't serialize and deserialize types as well as serde |
Very insightful. Seems to be what @DaviRain-Su is encountering as well. Supporting borsh does seem like it would take a decent commitment. While I think we want to end up supporting borsh, we don't have time to focus on that in the short term. However if this is a short-term requirement for you @DaviRain-Su then it does seem like the approach to take is to make sure that every type used by an ibc struct also derives borsh serialize/deserialize. And probably the same with parity-scale-codec. |
Now I have implemented codec and borsh codec for the timestamp type separately |
Summary
example case ClientId:
Problem Definition
Proposal
Acceptance Criteria
For Admin Use
The text was updated successfully, but these errors were encountered: