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
should be refactored to if !status.is_active() { ... }.
The status() is the status of the stored client state and its corresponding stored consensus state. So this doesn't include the provided ConsensusState. So its status needs to be checked locally.
Hi @rnbguy, I'd like to continue working on this issue. Could you please provide some guidance on how I should approach resolving it? I'd really appreciate any insights or suggestions you have. Thanks!
The status() is the status of the stored client state and its corresponding stored consensus state. So this doesn't include the provided ConsensusState. So its status needs to be checked locally.
Does this means we need to also store the ConsensusState to the validation context?
Does this means we need to also store the ConsensusState to the validation context?
We don't modify the store in the validation step. The Context is passed as an immutable reference in the validation calls. This is a convention in ibc-rs.
The way I see it, we may have to modify the status method to take the latest ConsensusState. Since this is an API-breaking change, we need to decide on this internally.
Bug Summary
only non-frozen status is checked at client creation. we should just check if the client is active.
Details
ibc-rs/ibc-core/ics02-client/src/handler/create_client.rs
Line 35 in 3b260e2
should be refactored toif !status.is_active() { ... }
.The
status()
is the status of the stored client state and its corresponding stored consensus state. So this doesn't include the providedConsensusState
. So its status needs to be checked locally.IBC-go also checks for active status, instead of just non-frozen status.
Version
v0.50.0
The text was updated successfully, but these errors were encountered: