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
Collators should keep around various informations (on disk) to be able to resubmit collations for unincluded blocks (also known as unincluded segment). With V3 candidate descriptor and V4 collator-protocol proposal is possible to submit an unincluded segment with every new block building iteration, and rely on the backing groups to fetch whichever collations they do not know about.
To be able to send the unincluded segment with every iteration, we must insert entries for each parablock with the following information during block import, and be able to relay them when needed:
parablock estimated submission time (can be for the scope of this task the moment when block_import task is started for the block)
Collators should keep around various informations (on disk) to be able to resubmit collations for unincluded blocks (also known as unincluded segment). With V3 candidate descriptor and V4 collator-protocol proposal is possible to submit an unincluded segment with every new block building iteration, and rely on the backing groups to fetch whichever collations they do not know about.
To be able to send the unincluded segment with every iteration, we must insert entries for each parablock with the following information during block import, and be able to relay them when needed:
RelayChainDataCache)Additional concerns: