Most of the large features on our roadmap in the Parachains Core team at Parity require significant changes to how collators build and propose blocks:
- With asynchronous backing, collators have greater flexibility in how many parachain blocks to build and which relay chain block to build off of.
- With the on-demand fee model, collators will want to scrape the relay chain bid queue and determine how much they’ll pay for an execution core and when.
- To make full use of elastic scaling, collators will want to be able to build multiple non-overlapping state transitions in parallel.
To enable these changes, @rphmeier has recently refactored how Cumulus handles parachain consensus by separating block proposal logic from the collator consensus mechanism – making it possible to write a variety of different collator consensus modules.
The design space for collators/sequencers is quite large and currently a major focal point of development work in other ecosystems. Polkadot was very early in launching decentralized collators in 2021 so it would be a shame to not stay on the cutting edge in this area.
In Parachains Core, our work in this area is focused on the collators necessary for supporting new parachain consensus features, which are quite a small subset of what’s possible. I want to draw attention to the recent Cumulus changes in hopes that they make it more straightforward for parachain development teams to implement special purpose collators for their own specific use cases.
A non-exhaustive list of ideas for collator consensus include:
- Proof of Stake using parachain tokens
- Quorum-based (Tendermint-style)
- Slot-based (Aura or Sassafras-style)
- Responsive (HotStuff family)
- Shared sequencing between multiple parachains
- Proposer/builder separation
More information can be found in the Cumulus issues and I’m always happy to talk to anyone interested in building in this area.