From f2150c216e28daf7182690dad7e7dcf3f9266dde Mon Sep 17 00:00:00 2001 From: bkchr Date: Thu, 8 Aug 2024 00:58:23 +0000 Subject: [PATCH] deploy: ab53bd3b75b4528d0bd27dc5e438751c85ff2c83 --- print.html | 4 +++- proposed/0100-xcm-multi-type-asset-transfer.html | 4 +++- searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 8 insertions(+), 4 deletions(-) diff --git a/print.html b/print.html index 40615a0..cbd05a9 100644 --- a/print.html +++ b/print.html @@ -890,6 +890,7 @@ For example, allows single XCM program execution to transfer multiple assets fro Asset Hub, over the bridge through Polkadot Asset Hub with final destination ParaP on Polkadot.

With current XCM, we are limited to doing multiple independent transfers for each individual hop in order to move both "interesting" assets, but also "supporting" assets (used to pay fees).

+

Note: Transferring assets that require different paths (chains along the way) is not supported within same XCM because of the async nature of cross chain messages. This new instruction, however, enables initiating transfers for multiple assets that take the same path even if they require different transfer types along that path.

Stakeholders