Skip to content
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

Elastic scaling: relay chain support for new candidate receipts #5045

Closed
sandreim opened this issue Jul 17, 2024 · 0 comments · Fixed by #5423
Closed

Elastic scaling: relay chain support for new candidate receipts #5045

sandreim opened this issue Jul 17, 2024 · 0 comments · Fixed by #5423

Comments

@sandreim
Copy link
Contributor

sandreim commented Jul 17, 2024

The implementation should follow guidelines in RFC #103

The relay chain must accept v2 candidate receipts and use their core information but fallback to the injected core index if the receipt is v1.

Test coverage:

  • unit tests for backwards compatibility with non elastic scaling parachains (using old descriptors)
  • unit tests backwards compatibility with elastic scaling parachains (MVP)
@sandreim sandreim converted this from a draft issue Jul 17, 2024
github-merge-queue bot pushed a commit that referenced this issue Oct 7, 2024
Closes #5045 and
#5046

<del>On top of
https://github.com/paritytech/polkadot-sdk/pull/5362</del>

TODO:
- [x] storage migration for allowed relay parents tracker 
- [x] check session index
- [x] PRdoc
- [x] tests
- [x] ensure UMP queue cannot be abused with this change
- [x] Zombienet runtime upgrade test

---------

Signed-off-by: Andrei Sandu <andrei-mihail@parity.io>
@github-project-automation github-project-automation bot moved this from Review in progress to Completed in parachains team board Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Pending Audit
Development

Successfully merging a pull request may close this issue.

1 participant