Implement ExportXcm and MessageDispatch for pallet-xcm-bridge-hub #2285
+339
−17
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.
This PR relates to:
XcmBlobHaulerAdapter
that supports dynamic configuration;pallet-xcm-bridge-hub
) to bothExportXcm
andMessageDispatch
to support backpressure on bridge/XCM queues.So this PR adds implementation of
ExportXcm
andMessageDispatch
to the recentpallet-xcm-bridge-hub
. In the future we'll migrate Rialto<>Millau and then other bridges to this pallet, sobridge_runtime_common::XcmBlobHaulerAdapter
andbridge_runtime_common::XcmBlobMessageDispatch
will dissolve. Right now it's just a code that isn't used anywhere, bu as I mentioned, I need it to progress on #2261.If we'll be implementing dynamic fees in V1 (without dynamic lanes), we'll probably keep using existing
bridge_runtime_common::XcmBlobHaulerAdapter
andbridge_runtime_common::XcmBlobMessageDispatch
. Then we'll need a totally separate PR to thepolkadot-staging
branch.