XCM transfer broken after #164

[clearloop]

Issue summary

• assetIndex.removeAsset

assetIndex.removeAsset failed: remoteAssetManager.XcmError:  Error occurred during XCM  

• remoteAssetManager.sendAddProxy

remoteAssetManager.sendAddProxy failed: remoteAssetManager.FailedToSendAddProxyXcm:  Thrown when sending an Xcm `pallet_proxy::add_proxy` failed

• remoteAssetManager.sendBond

remoteAssetManager.sendBond failed: remoteAssetManager.FailedToSendBondXcm:  Thrown when sending an Xcm `pallet_staking::bond` failed

---

Saw nothing changed outside asset-index and asset-registry but the XCM transfers start to be failed, the only diff in remote-asset-manager is a modification of a field in transfer-asset

Other information and links

[mattsse]

this rather looks like a Relay <-> Para connectivity issue, T::XcmSender::send_xcm(dest, xcm).

Sure PINT is already a parachain when you're running these commands?

[clearloop]

Sure PINT is already a parachain when you're running these commands?

Reasonable, I'll add a parachain check in e2e tests

[mattsse]

We talked about the finalized argument of polkadot-launch a while back, probably worth checking if this is helpful in that context.

[clearloop]

We talked about the finalized argument of polkadot-launch a while back, probably worth checking if this is helpful in that context.

Actually, the txs fail even after finalizing, for the finalization check, we already have in #153

[clearloop]

finalized argument of polkadot-launch

This https://github.com/paritytech/polkadot-launch/blob/6acc9187db0d1e2174cf3212a5ce8e80a34b47d3/config.json#L86 argument?

[mattsse]

finalized argument of polkadot-launch

This https://github.com/paritytech/polkadot-launch/blob/6acc9187db0d1e2174cf3212a5ce8e80a34b47d3/config.json#L86 argument?

yeah, https://github.com/paritytech/polkadot-launch/blob/cc3a1e5da490a8098039c5dec000c1ba89a2b7ae/README.md#finalization but I guess this is only for single txs and not the whole parachain onboarding process, however we're already waiting for the LAUNCH COMPLETE message, right https://github.com/ChainSafe/PINT/blob/main/js/finalize/index.ts#L11 ?

Was this perhaps introduced in #158 ?

[clearloop]

I thought about if it is caused by the upgrading, but 8c20762 still can run XCM transfers, but since PINT upgrades to v0.9.7, the docker images of statemint and polkadot should also be updated

[clearloop]

f50b967 still works LOL

[mattsse]

is it this: https://github.com/ChainSafe/PINT/blame/main/node/src/chain_spec.rs#L97 ?

[clearloop]

is it this: https://github.com/ChainSafe/PINT/blame/main/node/src/chain_spec.rs#L97 ?

Not sure, #172 works before merge, let me re-check this from the commit history of #164 QAQ