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
When using the juno command: oraid tx clock add-contract, we received the following error:
After debugging for a day, the closest I have got to understand this bug is that:
Cosmos SDK 0.50x has changed the way it handles gov proposals.
Instead of whitelisting the gov proposal content (like /juno.v1.clock.UpdateParamProposal), it recursively validates the entire MsgSubmitProposal message, consider any sub-messages within it also to be a Cosmos message as well.
Because /juno.v1.clock.UpdateParamProposal is not a message -> hence the error
The text was updated successfully, but these errors were encountered:
When using the
juno
command:oraid tx clock add-contract
, we received the following error:After debugging for a day, the closest I have got to understand this bug is that:
/juno.v1.clock.UpdateParamProposal
), it recursively validates the entireMsgSubmitProposal
message, consider any sub-messages within it also to be a Cosmos message as well./juno.v1.clock.UpdateParamProposal
is not a message -> hence the errorThe text was updated successfully, but these errors were encountered: