Sending bridged DOT from AH to parachain fails after upgrade #281
Comments
olanod
changed the title
|
Yes, it is an unintended regression. The fact that we could do it before the upgrade with the old extrinsic was just "lucky". Once on the parachain, the extrinsic could not send it anywhere else (not even back). The currently deployed runtime includes paritytech/polkadot-sdk#1672 and paritytech/polkadot-sdk#2388 which allow transfers of foreign assets in all directions within same consensus. Unfortunately, for bridged assets the "smart logic" added to the extrinsics in above PRs doesn't work anymore because the code cannot determine anymore which chain on this side of the bridge is allowed to act as a reserve for an asset on the other side of the bridge. For moving bridged assets around I created a new extrinsic paritytech/polkadot-sdk#3695 that allows the caller to force/override/specify reserve locations for "exotic" assets (where such information is not available in the runtime). I am also pushing for an offchain asset registry to hold this information: https://forum.polkadot.network/t/xcm-asset-registry/1168/3. |
|
@acatangiu will this be possible already in 1.2.2 ? how would the transfer extrinsic look like? |
Not possible yet in 1.2.2, I see on https://github.com/polkadot-fellows/runtimes/releases/ that 1.2.1, 1.2.2 and 1.2.3 were patch releases for other chains for other issues. Asset Hub runtimes latest release is still 1.2.0. I'll try to get it in #288, but I can't promise I'll make it (many things on my plate).
Example test for bridged asset AssetHub->Parachain - the actual call used here. In general, the emulated tests should cover all transfers scenarios and showcase how to do anything. Please let me know if you have a scenario not covered there. P.S.: there's many other goodies on the way too: https://forum.polkadot.network/t/xcm-user-and-developer-experience-improvements/4511/21 |
|
Backported for upcoming release: #311 |
…et transfers (#311) Bump `pallet-xcm` to 8.0.5 to include `transfer_assets_using_type_and_then()` call to facilitate moving bridged assets around the ecosystem. Example [test for bridged asset AssetHub->Parachain](https://github.com/paritytech/polkadot-sdk/blob/e0584a153df63ff138d12764085422ed06de548a/cumulus/parachains/integration-tests/emulated/tests/assets/asset-hub-westend/src/tests/hybrid_transfers.rs#L150C1-L156C54) - the actual call used [here](https://github.com/paritytech/polkadot-sdk/blob/e0584a153df63ff138d12764085422ed06de548a/cumulus/parachains/integration-tests/emulated/tests/assets/asset-hub-westend/src/tests/hybrid_transfers.rs#L57C1-L70C3). Example [test for bridged asset Parachain->AssetHub](https://github.com/paritytech/polkadot-sdk/blob/e0584a153df63ff138d12764085422ed06de548a/cumulus/parachains/integration-tests/emulated/tests/assets/asset-hub-westend/src/tests/hybrid_transfers.rs#L278C1-L285C54) - the actual call used [here](https://github.com/paritytech/polkadot-sdk/blob/e0584a153df63ff138d12764085422ed06de548a/cumulus/parachains/integration-tests/emulated/tests/assets/asset-hub-westend/src/tests/hybrid_transfers.rs#L76C2-L89C3). More details on the backported call available here: paritytech/polkadot-sdk#4462 Fixes #281 --------- Signed-off-by: Adrian Catangiu <[email protected]> Co-authored-by: Branislav Kontur <[email protected]> Co-authored-by: Bastian Köcher <[email protected]>
|
@olanod following the v1.2.4 upgrade, you can now do this with the following xt: Please confirm it works for you too. |
Before the last upgrade at block 6793666 there's an example of a limited reserve transfer assets of DOT from Kusama asset hub to parachain
2281which was successful, after the upgrade we can see another example at block 6814790 which fails with the errorInvalidAssetUnknownReserve. It seems like a regression unless sending such foreign asset to a Kusama parachain is expected to be done differently now.The text was updated successfully, but these errors were encountered: