Fix hrmp channels handling for polkadot chainspec #157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
majusko
approved these changes
Aug 23, 2023
|
can you do a |
xlc
approved these changes
Aug 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Looks like chainspecs for rococo & polkadot have a little bit different format. Specifically
rococohas some extra keyruntime_genesis_configwhile the polkdot does not. It seems that issue has been fixed partially forparaspallet initializationhttps://github.com/open-web3-stack/parachain-launch/blob/master/src/index.ts#L219
but hrmp pallet initialization is still broken (hrmp config from config file is ignored).
This PR fixes the problem