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
The upgrade sequence MUST also have a verification method so that chains can prove the upgrade sequence on the counterparty for the given channel upgrade.
Using the existing state verification keeper functions in 03-connection for reference:
Retrieve the ClientState and associated store using the provided connectionEnd
An error should be returned if the ClientState cannot be found
An error should be returned if the ClientState is inactive
Construct the MerklePath using the UpgradeSequencePath defined in 24-host
Invoke VerifyMembership using the associated ClientState
Summary
The upgrade sequence MUST also have a verification method so that chains can prove the upgrade sequence on the counterparty for the given channel upgrade.
Using the existing state verification keeper functions in
03-connection
for reference:ClientState
and associated store using the providedconnectionEnd
ClientState
cannot be foundClientState
is inactiveUpgradeSequencePath
defined in24-host
VerifyMembership
using the associatedClientState
Ref: https://github.com/cosmos/ibc/blob/master/spec/core/ics-004-channel-and-packet-semantics/UPGRADES.md#upgrade-sequence-path
Note the
ClientState
interface will contain a genericVerifyMembership
method following the completion of:For Admin Use
The text was updated successfully, but these errors were encountered: