-
Notifications
You must be signed in to change notification settings - Fork 791
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.
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
cumulus: ParachainBlockData
support multiple blocks
#6137
base: master
Are you sure you want to change the base?
Conversation
…ck-data-multiple-blocks
…ck-data-multiple-blocks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
) | ||
}); | ||
processed_downward_messages += crate::ProcessedDownwardMessages::<PSC>::get(); | ||
horizontal_messages.try_extend(crate::HrmpOutboundMessages::<PSC>::get().into_iter()).expect( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This limit of around 16k messages is now for all blocks in one PoV, not per block anymore right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
…ck-data-multiple-blocks
All GitHub workflows were cancelled due to failure one of the required jobs. |
This pull request adds support to
ParachainBlockData
to support multiple blocks at once. This basically means that cumulus based Parachains could start packaging multiple blocks into onePoV
. From the relay chain POV nothing changes and thesePoV
s appear like any otherPoV
. Internally thisPoV
then executes the blocks sequentially. However, all these blocks together can use the same amount of resources like a singlePoV
. This pull request is basically a preparation to support running parachains with a faster block time than the relay chain.This breaks the encoding of
ParachainBlockData
. It requires that the collators upgrade first before the runtime requiring the newParachainBlockData
is enacted. The collators will decide based on the api version ofCollectCollationInfo
, whichParachainBlockData
format they will send to the relay chain so that the validation code can interpret it correctly.