-
Notifications
You must be signed in to change notification settings - Fork 689
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
Testnet HostConfiguration migration (v11 to v12) #3503
Conversation
Signed-off-by: Andrei Sandu <[email protected]>
Signed-off-by: Andrei Sandu <[email protected]>
Signed-off-by: Andrei Sandu <[email protected]>
Signed-off-by: Andrei Sandu <[email protected]>
Signed-off-by: Andrei Sandu <[email protected]>
type V11HostConfiguration<BlockNumber> = configuration::HostConfiguration<BlockNumber>; | ||
|
||
#[derive(Clone, Encode, PartialEq, Decode, Debug)] | ||
pub struct V11HostConfiguration<BlockNumber> { |
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.
if nothing changed between v11 and v12, can we not simply do pub type V11HostConfiguration = V12HostConfiguration
?
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, that is what I've done initially but decided to make it a different struct to avoid any missuses as we have many unreleased migrations and another one not merged here: #3181
Superseded by: polkadot-fellows/runtimes#205 |
This one enables feature bit 1 (Elastic scaling MVP) but doesn't alter the structure.
Once the migration is done, upgraded nodes can include
CoreIndex
in backed candidates that are passed to the parachains inherent. Runtime already supports this injectedCoreIndex
. See #3231 and #3229