Skip to content

Conversation

@decentration
Copy link

This is so that we can execute xcm calls from sibling chains, specficially Turing chain, which allows for scheduling xcm calls at a later date and/or recurring.

Currently there is only AutoCompound as a ProxyType. But with MultiswapAsset other chains can execute a mangata based swap from their chian.

this is so that we can execute xcm calls from sibling chains, specficially Turing chain, which allows for scheduling xcm calls at a later date and/or recurring.
@chrisli30
Copy link

I fully support @decentration’s proposal. The Autocompound proxy type was added last year to enable Turing XCM automation for auto-compounding LP rewards. Having run securely for 12 months without any vulnerabilities, I believe it’s now safe to introduce another proxy type to unlock more automation opportunities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants