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
Add support for ibc.core.client.v1.ClientUpdateProposal using gov submit-proposal
Problem Definition
When attempting to submit an IBC client update governance proposal using provenanced tx gov submit-proposal, an error is thrown Error: no concrete type registered for type URL /ibc.core.client.v1.ClientUpdateProposal against interface *types.Msg.
ibc.core.client.v1.ClientUpdateProposal cannot be supported by gov submit-proposal since it is not of type sdk.Msg. It implements the legacy proposal type. You will have to continue using the legacy path for now.
In a future version (v.8.0.0) ibc-go will be deprecating the ibc.core.client.v1.ClientUpdateProposal and moving to the new sdk.Msg MsgRecoverClient instead that can be used with the gov submit-proposal method. https://github.com/cosmos/ibc-go/blob/0d524eca07e0a99519356f1767c5c4c267a31779/proto/ibc/core/client/v1/client.proto#L72C27-L72C43
@jtalis I would continue using the legacy method for submitting those proposals and plan on moving to MsgRecoverClient in a future release.
Summary
Add support for
ibc.core.client.v1.ClientUpdateProposal
usinggov submit-proposal
Problem Definition
When attempting to submit an IBC client update governance proposal using
provenanced tx gov submit-proposal
, an error is thrownError: no concrete type registered for type URL /ibc.core.client.v1.ClientUpdateProposal against interface *types.Msg
.The following proposal json was attempted:
Submitting the proposal using the submit legacy path works fine. See https://explorer.test.provenance.io/tx/AEB84C595871E0F009309E6CE3815E1F345E88DEFC5F299959998E05674CDDD8/17341185 for an example of the proposal submitted using the legacy flow.
Proposal
Add support for
ibc.core.client.v1.ClientUpdateProposal
usinggov submit-proposal
For Admin Use
The text was updated successfully, but these errors were encountered: