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
We added the possibility of sending the full parent head data (not just the hash as it used to be) for elastic scaling.
This was done in #3521, only for paras that have multiple assigned cores.
However, having this always present would allow for some simplifications in the validator side of the collator protocol. We'd no longer need to keep candidates in
I propose we always send the full parent head data from the collator. This won't enable us to do the simplification I mentioned above rightaway. That can only be done once all collators upgrade
The text was updated successfully, but these errors were encountered:
We added the possibility of sending the full parent head data (not just the hash as it used to be) for elastic scaling.
This was done in #3521, only for paras that have multiple assigned cores.
However, having this always present would allow for some simplifications in the validator side of the collator protocol. We'd no longer need to keep candidates in
polkadot-sdk/polkadot/node/network/collator-protocol/src/validator_side/mod.rs
Line 408 in 7211692
I propose we always send the full parent head data from the collator. This won't enable us to do the simplification I mentioned above rightaway. That can only be done once all collators upgrade
The text was updated successfully, but these errors were encountered: