Upgrade polkadot-sdk to version 1.7.0 #2688
Closed
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.
What does it do?
This PR updates polkadot-sdk dependencies to version 1.7.2.
What important points reviewers should know?
Polkadot-sdk version 1.7.0 includes XCMv4, which removes the
Multi
prefix in many places, changes some XCM syntax (examples below) and removesAbstract
variant fromAssetId
.New syntax for building locations and junctions
Now junctions are built using the following methods:
or
And they are matched like so:
This syntax is mandatory in v4, and has been also implemented for v2 and v3 for easier migration.
This was needed to make all sizes smaller.
Removed Abstract asset id
Now assets are just constructed as follows:
Is there something left for follow-up PRs?
NO
Are there relevant PRs or issues in other repositories (Polkadot-sdk, Frontier)?
Runtime API
Identity pallet:
XCM:
Message Queue
as DMP and XCMP dispatch queue paritytech/polkadot-sdk#1246XCM benchmarks
reserve_transfer_assets
to support remote reserves paritytech/polkadot-sdk#1672RewardDestination
RewardDestination::Controller
paritytech/polkadot-sdk#2380RPC
Client
sc-block-builder
: RemoveBlockBuilderProvider
paritytech/polkadot-sdk#2099What value does it bring to the blockchain users?