#11239) # Description This PR achieves the following: 1) removes the assumption that the scheduling parent sent with a candidate descriptor is an active leaf on the collator-side 2) adds a minor reputation penalty for collators advertisements with an invalid scheduling parent, which ends up in a collator ban and disconnect only when abuse happens (see #11339). 3) checks on the validator_side that the candidate descriptor's scheduling parent is the rc block corresponding to the last finished rc slot's block. ## Integration N/A ## Review Notes Fixes #11169 Cumulus side here: #11241 Tests were done against the cumulus PR + the corresponding scheduling parent picking logic when building block (async backing with v2/v3 collations). Additional tests were made for the case of elastic scaling too (v2 & v3 alike). As a bonus, the changed logic removes the `slot_offset` for V3 collations building. --------- Signed-off-by: Iulian Barbu <iulian.barbu@parity.io> Co-authored-by: eskimor <robert@gonimo.com> Co-authored-by: eskimor <eskimor@noreply.com> Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: eskimor <jfanatiker@gmx.at>

Fix active leaf check to be slot based (see design) #11169

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions