In the proxy pallet's do_proxy function, a newly authenticated origin is constructed from the real account. This is explicitly done.
Is there a particular reason for this?

Can I just use the same origin and then use set_caller_from to set it to real?
I would like to do this to ensure that the restrictions (one particular call filter) I apply to the origin in utility.batch are sustained even if utility.batch wraps proxy calls to attempt to avoid the restrictions.

Is there a better way to do this?

Thank you.
Please let me know if more info is required


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.