You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Parachain consensus is restricted to a subset of the relay chain validators via themaxValidators configuration parameter. The plan is to remove the parameter, but until then we will gradually increase it's value as we improve the protocol and performance characteristics of the implementation. maxValidators is bumped to higher values only if key performance metrics, specifically parachain block times and finality lag do not degrade when more validators participate in parachain consensus.
After improving our tooling for profiling, gathering metrics and debugging we identified bottlenecks which we are currently addressing.
Experiments and potential improvements are tested on Versi before enabling them on value bearing chains like Kusama and Polkadot. After a battery of tests successfully ran on Versi we have already bumped the number of paravalidators from 200 to 250 on Kusama and we are currently monitoring the key metrics.
Increase the number of parachain validators from 200 to 250 (supporting up to 70 parachains) on Kusama
Increase the number of parachain validators from 250 to 300 (supporting up to 70 parachains) on Kusama
Increase the number of parachain validators from 200 to 300 (supporting up 70 parachains) on Polkadot
We've learned from previous tests, that it is already possible for Versi to operate within parameters with 500 paravalidators and 70 parachains, but we've also identified that availability recovery is getting slower as the load on the network I/O increase. Supporting 100 parachains would create even more network load so this needs to be addressed for this milestone.
Parachain consensus is restricted to a subset of the relay chain validators via the
maxValidatorsconfiguration parameter. The plan is to remove the parameter, but until then we will gradually increase it's value as we improve the protocol and performance characteristics of the implementation.maxValidatorsis bumped to higher values only if key performance metrics, specifically parachain block times and finality lag do not degrade when more validators participate in parachain consensus.The scalability project board is available here: Road to 1k paravalidators and 200 parachains
After improving our tooling for profiling, gathering metrics and debugging we identified bottlenecks which we are currently addressing.
Experiments and potential improvements are tested on Versi before enabling them on value bearing chains like Kusama and Polkadot. After a battery of tests successfully ran on Versi we have already bumped the number of paravalidators from
200to250on Kusama and we are currently monitoring the key metrics.Q2 Plan
approval distribution: trigger assignment/votes resend based on approval checking lag polkadot#7038Q2 milestones:
200to250(supporting up to 70 parachains) on Kusama250to300(supporting up to 70 parachains) on Kusama200to300(supporting up 70 parachains) on PolkadotWe've learned from previous tests, that it is already possible for Versi to operate within parameters with 500 paravalidators and 70 parachains, but we've also identified that availability recovery is getting slower as the load on the network I/O increase. Supporting 100 parachains would create even more network load so this needs to be addressed for this milestone.
Q4 Plan
PeerViewChangemessages with priority polkadot-sdk#577availability-recovery: fetch available data from approval checkers polkadot-sdk#575Q1 2024 milestone:
300to500(supporting up to 100 cores) on Kusama2024