《最强大脑》首场国际赛中国战队告负

Question

I am experiencing an issue with proxy transactions on Westend Asset Hub. The proxy transaction shows as executed successfully, but the underlying function doesn't execute properly.

Transaction Details:

• Sender Account: 5E92HEC2bFWNipDcdhre93L3UAqFNFgch3kJy83qwpvEL4SP
• Real Account: 5GaEfMMcg12Q7UF8wjZ6UXCurWRSbtyYSMUrD3F4nFdM7qAA
• Proxy Extrinsics shown as Success here
• Same Proxy Extrinsics shown as Failed here
• If I click in each of the extrinsics I see a system (ExtrinsicSuccess) event which makes me think that there is no error and the extrinsic completed successfully.

The steps were done correctly

• Set up a staking proxy from the real account (extrinsic)
• Try to bond funds from the Staking Proxy (for the real account) to create the initial staking ledger (extrinsics)
• Try to set_payee from the Staking Proxy (for the real account) (extrinsic)

The issue is found only when clicking in any of the extrinsics, then clicking under proxy (ProxyExecuted) event and there is a CallFiltered call with The origin filter prevent the call to be dispatched. doc. This seems like an error since in other working examples like this one, this should show result Ok when there are no errors.

Why is the proxy transaction marked as successful when the actual proxied call is being blocked by the origin filter? How can I fix this?

Thank you Ankan and Oliver in helping debugging this.

Answer 1

The issue is that the account has two proxy delegations; one for Assets management and one for Staking relating things.

[
  [
    {
      delegate: 5E92HEC2bFWNipDcdhre93L3UAqFNFgch3kJy83qwpvEL4SP
      proxyType: Assets
      delay: 0
    }
    {
      delegate: 5E92HEC2bFWNipDcdhre93L3UAqFNFgch3kJy83qwpvEL4SP
      proxyType: Staking
      delay: 0
    }
  ]
  10,053,000,000
]

The user has to use the force_proxy_type argument of the proxy extrinsic. Internally, it just picks the first proxy and tries to dispatch the inner Staking call. In this case, that is an Assets proxy - not a Staking proxy, hence it fails. If they retry and set the force_proxy_type to Staking then it should work.

The confusing part is that the Proxy extrinsic reports a successful outcome instead of just returning an error. It does emit an event to indicate the error, but that is a bit hard to see. I hope that multisig UIs are aware of this and automatically set the argument.