Using Proxy Accounts

Does anyone know a practical way to use a proxy account in the Acala Dapp? the pallet certainly exists in the runtime and you can set proxies in the Polkadot.js/apps UI. Nonetheless, I don’t think there’s any way to actually use it in the default Acala app.

The core of the issue is that none of the extensions really support this, and even if so, unlike other parachain dapps, the Acala one only supports Polkadot js extension. Ideally, these extensions would detect the existence of proxies, and provide functionality around it.

related: Support (manually set) proxied calls · Issue #1035 · polkadot-js/extension · GitHub

Lastly, a simple workaround would be for the Acala dapp to simply print the details of the call that it is trying to sign with the extension to the console, and the hardcore user manually re-entering that in the Polkadot.js/apps website.