Update Polkadot-SDK #2175
Closed
Update Polkadot-SDK #2175
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add AssetTransferFilter trait for configuring transfer types. Implement it for XcmExecutor based on existing executor teleports and reserves configuration. Filter assets on pallet-xcm::limited_teleport_assets() based on above.
…erves 'reserve_transfer_assets()' assumed all provided `assets` (fees included) have same, local reserve. This commit enhances the extrinsic to support various scenarios: - transferring assets with reserve on destination, - transferring assets with reserve on remote/third-party chain, - transferring assets with reserve different than the reserve of the asset to be used as fees - meaning can use to transfer random asset with random reserve while using DOT for fees on all involved chains, even if local chain is NOT a reserve location of DOT (aka most chains), - transferring assets with any type of local/dest/remote reserve while using fees which can be teleported between involved chains. All of the above is done by pallet inner logic without the user having to specify which scenario/reserves/teleports/etc. The correct scenario and corresponding XCM programs are identified, and respectively, built automatically based on runtime configuration of trusted teleporters and trusted reserves. Current limitations: - while `fees` and "non-fee" `assets` CAN have different reserves (or fees CAN be teleported), the remaining "non-fee" `assets` CANNOT have different reserve locations (this is also implicitly enforced by `MAX_ASSETS_FOR_TRANSFER=2`, but this can be safely increased in the future). - `fees` and "non-fee" `assets` CANNOT have **different remote** reserves (this can also be supported in the future, but adds even more complexity while possibly not being worth it - we'll see what the future holds).
…et-xcm-fully-support-reserve-transfers
…-locations Remove gateway contract locations from Assets
…et-xcm-fully-support-reserve-transfers
* configures ethereum router * adds benchmarks and fmt --------- Co-authored-by: claravanstaden <Cats 4 life!>
…-from-adrian # Conflicts: # Cargo.lock # cumulus/pallets/dmp-queue/src/lib.rs # cumulus/parachains/integration-tests/emulated/bridges/bridge-hub-rococo/Cargo.toml # cumulus/parachains/runtimes/assets/asset-hub-rococo/src/lib.rs # cumulus/parachains/runtimes/assets/asset-hub-rococo/src/xcm_config.rs # cumulus/parachains/runtimes/bridge-hubs/bridge-hub-rococo/src/lib.rs # cumulus/parachains/runtimes/bridge-hubs/bridge-hub-rococo/src/xcm_config.rs
|
User @claravanstaden, please sign the CLA here. |
bkontur
pushed a commit
that referenced
this pull request
May 13, 2024
bkontur
pushed a commit
that referenced
this pull request
May 14, 2024
bkontur
pushed a commit
that referenced
this pull request
May 15, 2024
bkontur
pushed a commit
that referenced
this pull request
May 15, 2024
bkontur
pushed a commit
that referenced
this pull request
May 15, 2024
bkontur
pushed a commit
that referenced
this pull request
May 15, 2024
bkontur
pushed a commit
that referenced
this pull request
May 16, 2024
bkontur
pushed a commit
that referenced
this pull request
May 17, 2024
bkontur
pushed a commit
that referenced
this pull request
May 17, 2024
bkontur
pushed a commit
that referenced
this pull request
May 17, 2024
bkontur
pushed a commit
that referenced
this pull request
May 20, 2024
bkontur
pushed a commit
that referenced
this pull request
May 21, 2024
bkontur
pushed a commit
that referenced
this pull request
May 22, 2024
bkontur
pushed a commit
that referenced
this pull request
May 23, 2024
bkontur
pushed a commit
that referenced
this pull request
May 30, 2024
bkontur
pushed a commit
that referenced
this pull request
Jun 4, 2024
bkontur
pushed a commit
that referenced
this pull request
Jun 5, 2024
bkontur
pushed a commit
that referenced
this pull request
Jun 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fetches updates from upstream https://github.com/paritytech/polkadot-sdk/pull/1672/files.