-
Notifications
You must be signed in to change notification settings - Fork 775
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
collator protocol: Provide parent head data #3128
Comments
2 tasks
ordian
added
T9-cumulus
This PR/Issue is related to cumulus.
and removed
T9-cumulus
This PR/Issue is related to cumulus.
labels
Mar 11, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 15, 2024
Fixes #3128. This introduces a new variant for the collation response from the collator that includes the parent head data. For now, collators won't send this new variant. We'll need to change the collator side of the collator protocol to detect all the cores assigned to a para and send the parent head data in the case when it's more than 1 core. - [x] validate approach - [x] check head data hash
github-project-automation
bot
moved this from Review in progress
to Completed
in parachains team board
Mar 15, 2024
reopening until #3521 is merged |
dharjeezy
pushed a commit
to dharjeezy/polkadot-sdk
that referenced
this issue
Mar 24, 2024
…ytech#3302) Fixes paritytech#3128. This introduces a new variant for the collation response from the collator that includes the parent head data. For now, collators won't send this new variant. We'll need to change the collator side of the collator protocol to detect all the cores assigned to a para and send the parent head data in the case when it's more than 1 core. - [x] validate approach - [x] check head data hash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add an additional (backwards compatibility) advertise collation message, which triggers a different collation fetch request (requesting also the head data of the parent) -> Make use of that head data in candidate validation.
The text was updated successfully, but these errors were encountered: