Skip to content
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

wasm wrapped client and consensus state at counterparty #159

Closed
rnbguy opened this issue May 13, 2024 · 0 comments · Fixed by #170
Closed

wasm wrapped client and consensus state at counterparty #159

rnbguy opened this issue May 13, 2024 · 0 comments · Fixed by #170

Comments

@rnbguy
Copy link
Member

rnbguy commented May 13, 2024

Currently, sovereign-ibc module expects its client and consensus state stored at counterparty as a direct serialization of its Any form.

But in wasm-08 enabled cosmos-sdk chains, sovereign client and consensus state will be stored after being wrapped in their corresponding wasm types.

This is important as during the connection handshakes, ibc module verifies its host client states at its counterparty state root. Depending on the serialization type - the provided proof will succeed or fail.

So, the current client and consensus state implementation needs to be improved to handle both cases:

  • native Any serialization
  • Any serialization of wasm wrapper types
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
1 participant