Call filter supports call that triggered indirectly like Utility.batch and sudo

[ianhe8x]

for batch and sudo extrinsics, method is not the actually extrinsic so current filter won't be able to pick these tx out.

[ianhe8x]

I'm glad that we picked the name callHandler instead of extrinsicHandler, now it is very clear that what we care about is call and a call can be carried out in different ways, an extrinsic signed and submitted by the call origin account is one way, other ways include Utility.batch, Utility.batch_all, sudo, council.execute, scheduler

What makes it more complicated is these means can be used together. E.g counsil vote an action and it is to be carried out via scheduler module which eventually make it happen at a block in the future.

[ianhe8x]

Extend the list of indirect call execution with Multisig.as_multi and Proxy.proxy()

examples: https://polkadot.subscan.io/extrinsic/0xff8639407212bb60ea41feafcfd2813d8c33d95935cac1f082ddf2a0ec5b80f4?event=4101238-3

[jiqiang90]

Ref community built tool: https://github.com/nova-wallet/subquery-call-visitor