-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
XCM autoteleport issues #9073
Comments
Hey @exezbcz , Could you ellaborate if you tried to send max amount over or you inputed random lower amount? Thanks! With kind regards, |
I think it is because in the sidebar with assets, we round the amounts
|
Thanks for the information @exezbcz , With kind regards, |
Hey @exezbcz , What we noticed however is, that teleport max does not work and on Kusama Asset Hub leads to loss of entire funds. The failed transactions do not show in subscan so they are harder to trace. We have also tested Polkadot and Polkadot Asset Hub, as expected, these work just fine because they do not have latest runtime yet. ParaSpell is soon going to introduce keep alive feature that would allow you to only send transfers that will keep accounts alive if opted. This can be possibly used in teleport max option to ensure, that there will be no loss of funds. |
We have tested on other UI DEX Platforms (Karura, Basilisk), every Platform results in total loss of assets if MAX amount is transferred. |
We have opened an issue in the Polkadot SDK repo. This is an internal Polkadot issue as it seems. |
looks like we have some issues here, it does not work even though signing etc. went through
Screen.Recording.2024-01-20.at.19.55.11.mov
on subscan it does not even show
Ft3LDkYXYzgxBYMJnft1cJBgAGjCoVZh9ioj7VDbYn9PpDJ
The text was updated successfully, but these errors were encountered: