You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: