mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-26 06:27:58 +00:00
Adrian Catangiu
1e971b8d2a
# Description Add `transfer_assets_using()` for transferring assets from local chain to destination chain using explicit XCM transfer types such as: - `TransferType::LocalReserve`: transfer assets to sovereign account of destination chain and forward a notification XCM to `dest` to mint and deposit reserve-based assets to `beneficiary`. - `TransferType::DestinationReserve`: burn local assets and forward a notification to `dest` chain to withdraw the reserve assets from this chain's sovereign account and deposit them to `beneficiary`. - `TransferType::RemoteReserve(reserve)`: burn local assets, forward XCM to `reserve` chain to move reserves from this chain's SA to `dest` chain's SA, and forward another XCM to `dest` to mint and deposit reserve-based assets to `beneficiary`. Typically the remote `reserve` is Asset Hub. - `TransferType::Teleport`: burn local assets and forward XCM to `dest` chain to mint/teleport assets and deposit them to `beneficiary`. By default, an asset's reserve is its origin chain. But sometimes we may want to explicitly use another chain as reserve (as long as allowed by runtime `IsReserve` filter). This is very helpful for transferring assets with multiple configured reserves (such as Asset Hub ForeignAssets), when the transfer strictly depends on the used reserve. E.g. For transferring Foreign Assets over a bridge, Asset Hub must be used as the reserve location. # Example usage scenarios ## Transfer bridged ethereum ERC20-tokenX between ecosystem parachains. ERC20-tokenX is registered on AssetHub as a ForeignAsset by the Polkadot<>Ethereum bridge (Snowbridge). Its asset_id is something like `(parents:2, (GlobalConsensus(Ethereum), Address(tokenX_contract)))`. Its _original_ reserve is Ethereum (only we can't use Ethereum as a reserve in local transfers); but, since tokenX is also registered on AssetHub as a ForeignAsset, we can use AssetHub as a reserve. With this PR we can transfer tokenX from ParaA to ParaB while using AssetHub as a reserve. ## Transfer AssetHub ForeignAssets between parachains AssetA created on ParaA but also registered as foreign asset on Asset Hub. Can use AssetHub as a reserve. And all of the above can be done while still controlling transfer type for `fees` so mixing assets in same transfer is supported. # Tests Added integration tests for showcasing: - transferring local (not bridged) assets from parachain over bridge using local Asset Hub reserve, - transferring foreign assets from parachain to Asset Hub, - transferring foreign assets from Asset Hub to parachain, - transferring foreign assets from parachain to parachain using local Asset Hub reserve. --------- Co-authored-by: Branislav Kontur <bkontur@gmail.com> Co-authored-by: command-bot <>
39 lines
2.1 KiB
Plaintext
39 lines
2.1 KiB
Plaintext
# Schema: Polkadot SDK PRDoc Schema (prdoc) v1.0.0
|
|
# See doc at https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json
|
|
|
|
title: "pallet-xcm: add new extrinsic for asset transfers using explicit reserve"
|
|
|
|
doc:
|
|
- audience: Runtime User
|
|
description: |
|
|
pallet-xcm has a new extrinsic `transfer_assets_using_type` for transferring
|
|
assets from local chain to destination chain using an explicit XCM transfer
|
|
types for transferring the assets and the fees:
|
|
- `TransferType::LocalReserve`: transfer assets to sovereign account of destination
|
|
chain and forward a notification XCM to `dest` to mint and deposit reserve-based
|
|
assets to `beneficiary`.
|
|
- `TransferType::DestinationReserve`: burn local assets and forward a notification to
|
|
`dest` chain to withdraw the reserve assets from this chain's sovereign account and
|
|
deposit them to `beneficiary`.
|
|
- `TransferType::RemoteReserve(reserve)`: burn local assets, forward XCM to `reserve`
|
|
chain to move reserves from this chain's SA to `dest` chain's SA, and forward another
|
|
XCM to `dest` to mint and deposit reserve-based assets to `beneficiary`. Typically
|
|
the remote `reserve` is Asset Hub.
|
|
- `TransferType::Teleport`: burn local assets and forward XCM to `dest` chain to
|
|
mint/teleport assets and deposit them to `beneficiary`.
|
|
By default, an asset's reserve is its origin chain. But sometimes we may want to
|
|
explicitly use another chain as reserve (as long as allowed by runtime IsReserve
|
|
filter).
|
|
This is very helpful for transferring assets with multiple configured reserves
|
|
(such as Asset Hub ForeignAssets), when the transfer strictly depends on the used
|
|
reserve location.
|
|
|
|
E.g. For transferring a bridged Foreign Assets between local parachains, Asset Hub
|
|
or the parachain that bridged the asset over must be used as the reserve location.
|
|
Same when transferring bridged assets back across the bridge, the local bridging
|
|
parachain must be used as the explicit reserve location.
|
|
|
|
crates:
|
|
- name: pallet-xcm
|
|
bump: minor
|