-
Notifications
You must be signed in to change notification settings - Fork 379
Enable collation with external relay chain full node #989
Comments
CC @drahnr maybe you have some input on the |
I think implementing |
Hi, Sebastian! Is there any way to contribute to this issue? Looks like collators are almost finished, is that right? |
Hey @gregzaitsev, I have a branch where this works, some refactorings and polish needs to be done still. |
@skunert I assume you are aware, a few weeks ago a change landed that splits the network bridge into two, incoming and outgoing messages, so the initial diagram might need some adjustments :) |
As discussed in #545 we want to support running the collator relay chain node as its own process.
After #963 lands, we are in a position to run a parachain full node without running a relay chain full node internally. To run a proper parachain collator, we miss some of the subsystems usually running inside the full node. They do not offer an RPC interface, so I plan to start the relevant subsystems inside the collator.
Relevant Subsystems
After checking the code, I found that the following subsystems are involved:
The Availability store should be optional for now since the data we request from it will not be available inside the collator anyway and will then be requested from the Network Bridge.
Implementation Plan
OverseerGen
that will replace unused Subsystem with dummies that drain channelsRelated discussion in paritytech/polkadot#4763
The text was updated successfully, but these errors were encountered: