Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure we support dispatching messages directly at bridge hub #2378

Open
2 tasks
svyatonik opened this issue Aug 23, 2023 · 0 comments
Open
2 tasks

Make sure we support dispatching messages directly at bridge hub #2378

svyatonik opened this issue Aug 23, 2023 · 0 comments

Comments

@svyatonik
Copy link
Contributor

There are some use cases for dispatching message at the target bridge hub. So it's one hop less than our regular path (source_chain -> source_bridge_hub -> target_bridge_hub -> target_chain - assume that target_bridge_hub is the target_chain). We need to support in in v2:

  • the pallet-xcm-bridge-hub implements MessageDispatch trait. Right now (afaik) it uses the xcm_builder::BridgeBlobDispatcher, which calls the send_xcm. We need to be sure that either send_xcm supports sending to the same chain or we need to use some other dispatcher;
  • we need some process to open the bridge (open_bridge call of the pallet-xcm-bridge-hub) at the target BH. Relay chain governance?
@EmmanuellNorbertTulbure EmmanuellNorbertTulbure transferred this issue from paritytech/parity-bridges-common Aug 25, 2023
@the-right-joyce the-right-joyce transferred this issue from paritytech/polkadot-sdk Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants