andrew-ifrita

Marking as won't fix as we are dropping support for `asset-transfer-api` in favor of ParaSpell. See more in this issue: https://github.com/paritytech/asset-transfer-api/issues/652

@rockbmb and I discussed this briefly after the Westend AHM and he helped me investigate a bit. > Hm, I just tried: > > 1. sending exactly the (relay's) ED...

This is actually a duplicate of https://github.com/paritytech/asset-transfer-api/issues/431 but I will close that issue instead as it is a bit dated and the author hasn't been active for some time.

Marking as won't fix as we are dropping support for `asset-transfer-api` in favor of ParaSpell. See more in this issue: https://github.com/paritytech/asset-transfer-api/issues/652

@jpinhog Can you confirm which version was `asset-transfer-api` was being used?

@jpinhog Can you share how `createTransferTransaction(...)` is being used to generate the XCMs here? That will help me recreate the issue and resolve the problem.

@jpinhog The main difference in the examples provided seems to be sending USDT (working example) vs DOT (failing example). This seems sensible since Astar doesn't support DOT. Was this the...

> Hi [@andrew-ifrita](https://github.com/andrew-ifrita), below is the full payload for createTransferTransaction. We’re using **DOT** as the **xcmFeeAsset**. Should the **xcmFeeAsset** always match the **tokenCode** used in the transfer? For example, if...

I started putting together a test case in this PR, https://github.com/paritytech/asset-transfer-api/pull/626. For sanity sake I also tried doing the following on Kusama Asset Hub -> Shiden ```ts const ata =...

Yes, I am able to recreate this as well. I will take a deeper look. At first glance it looks like the xcmFeeAsset is being mishandled as the response doesn't...