Use the selected backend worker (Libp2p vs Litep2p) #3595
Merged
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.
What does it do?
Context: paritytech/polkadot-sdk#8461
This PR updates Moonbeam’s node startup wiring so the selected P2P backend is actually used. Instead of always building the networking stack with the
libp2pworker type,start_nodenow branches onparachain_config.network.network_backendand instantiates the appropriate backend (Libp2p vs Litep2p). TheLitep2pis the default on recent polkadot-sdk versions.Context
When a node is configured to run with Litep2p, the service should construct the corresponding networking backend. This change ensures Moonbeam respects the configured backend selection and avoids mismatched network worker types.