-
Notifications
You must be signed in to change notification settings - Fork 1
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
When possible, use IBC types from ibc-rs #150
Comments
I will list down some current examples of dirty hacks. This issue should resolve them. Almost all Cairo domain types should reuse Packetibc-starknet/relayer/crates/starknet-chain-components/src/impls/messages/packet.rs Lines 237 to 364 in c13b888
TracePathibc-starknet/relayer/crates/starknet-chain-components/src/impls/messages/packet.rs Line 268 in 7c07515
Connection Versionibc-starknet/relayer/crates/starknet-chain-components/src/impls/messages/connection.rs Lines 97 to 131 in c13b888
|
We should reuse types like
ClientId
,ConnectionId
,Packet
, etc. That would make it significantly easier to reuse the Cosmos implementations, which assume that the counterparty has these types. Otherwise, we have to copy over the Cosmos implementations, and perform minor tweaks to convert between the types.The way we implement Cairo encoding means that we can easily implement them for non-owned types from ibc-rs. The main difference is that we will need to implement
FieldGetter
for the ibc-rs types, and then use encoders likeEncodeFieldWithGetter
to pass in the field getters explicitly.The text was updated successfully, but these errors were encountered: