We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems that when authz actions happen differently than their vanilla counterparts.
It looks like the nested messages may still be encoded with protobuf, in which case we will need to decode them in the handler.
Example authz message body (see investigation-query.gql):
{ "grantee": "fetch1m5hgzum68rjf4c7zhezgkj8hlnmr0kgh9uj0g8", "msgs": [ { "typeUrl": "/cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward", "value": { "0": 10, "1": 44, "2": 102, ... } }, { "typeUrl": "/cosmos.staking.v1beta1.MsgDelegate", "value": { "0": 10, "1": 44, "2": 102, ... } ] }
Handler exists for authz's MsgExec message which:
MsgExec
Msgs
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Background
It seems that when authz actions happen differently than their vanilla counterparts.
It looks like the nested messages may still be encoded with protobuf, in which case we will need to decode them in the handler.
Example authz message body (see investigation-query.gql):
Acceptance Criteria
Handler exists for authz's
MsgExec
message which:checks that it's transaction was successful and bails if notMsgs
and calls the primitive message handler, and any respective message handler functionThe text was updated successfully, but these errors were encountered: