-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support transfering multiple assets(now only one) in orml-xtokens #663
Comments
Just wanted to cross-post some a thought I had in bifrost-finance/bifrost#420 here too HI! Just curious about the same problem (sending statemine assets back to statemine) and I am wondering a few things about this implementation:
|
The reserve chain of KSM is Kusama, not Statemine, so we will simply reject direct KSM transfer from Statemine. |
How are you going to handle sending statrmine assets back to statemine then? given that statemine fees can only be paid in KSM, I am guessing the sovereign account in statemine will need to have KSM and the transferred asset somehow. |
Yeah XCM basically doesn't offer much ways to manage fees on sovereign account (e.g. you can't really track how much fee is charged). So the simple solution is just topup the sovereign account on Statemine somehow. It can be done manually, or should be possible to do a reserve transfer of KSM to Kusama and teleport it to Statemine parachain sovereign account. |
resolved in #658 |
related issues and prs:
paritytech/cumulus#827
paritytech/cumulus#806
paritytech/polkadot#4470
wrap xcm as following when send statemine asset back:
https://github.com/bifrost-finance/bifrost/blob/c7eb1bef7abfdeb6562aeda29ab76805308b77f5/pallets/salp/src/lib.rs?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L1012-L1031
The text was updated successfully, but these errors were encountered: