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.

Sign up for GitHub

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

Jump to bottom

Backport (some) xcm-bridge-hub and xcm-bridge-hub-router pallet changes to master #2354

Closed
svyatonik opened this issue Aug 16, 2023 · 1 comment
Closed

Backport (some) xcm-bridge-hub and xcm-bridge-hub-router pallet changes to master #2354

svyatonik opened this issue Aug 16, 2023 · 1 comment
Assignees
@svyatonik
Labels
A-chores Something that has to be done, as part of regular maintenance
Milestone
Kusama <> Polkado...

Comments

@svyatonik
Copy link
Contributor

Main changes are now in polkadot-staging and dynamic-fees-v1 branches. Master branch has some version without recent changes. So we need to backport changes from polkadot-staging and dynamic-fees-v1 to master. However I'd like to exclude #2318 from master - in v2 we'll probably have the paritytech/polkadot-sdk#5062, so we won't need to send XCM messages between chains
@svyatonik svyatonik added the A-chores Something that has to be done, as part of regular maintenance label Aug 16, 2023
@svyatonik svyatonik self-assigned this Aug 16, 2023
@svyatonik
Copy link
Contributor Author

closed by #2372

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@svyatonik svyatonik

Labels
A-chores Something that has to be done, as part of regular maintenance
Projects
None yet
Milestone
Kusama <> Polkadot Parachain Bridge V2
Development

No branches or pull requests
1 participant
@svyatonik