This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
Add commons crate for BridgeHub runtimes [do not merge] #22
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 adds a crate
bridge-hub-common
with common utilities for all BridgeHub runtimes (similar to the purpose of theasset-hub-common
crate).It is not meant to hold runtime config or utilities that are specific to either Snowbridge or ParityBridge. There are other crates for that. Rather, it is meant to handle cross-cutting concerns that affect all bridges on BridgeHub.
The crate initially provides specialized config for the
MessageQueue
pallet. See paritytech#2146 for background and discussion.Changes:
AggregateMessageOrigin
that identifies message queues belonging to either XCMP or to SnowbridgeBridgeHubMessageRouter
, a message processor that routes messages either to XCMP or to Snowbridge.