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
With paritytech/polkadot#2423 in place we are requesting availability chunks from validators in the backing group of that candidate. Problem is not all of them will be actual backers, which results in needless requests. Either in parallel - wasting bandwidth or in sequence on failure - wasting time.
Solutions:
Either record actual backers on chain in OccupiedCore in a backer bitfield for example. We would need to do some unification of backer bitfield (bitwise OR) because different subsets of backers might appear in different chains and we'd want to request from anyone who signed a statement.
Backers send out notifications via gossip or directly once they backed a candidate.
Collect that information from statement distribution already - backers already gossip, that they backed a candidate .. that should work as well, but I will need to read up on statement distribution first.
The text was updated successfully, but these errors were encountered:
With paritytech/polkadot#2423 in place we are requesting availability chunks from validators in the backing group of that candidate. Problem is not all of them will be actual backers, which results in needless requests. Either in parallel - wasting bandwidth or in sequence on failure - wasting time.
Solutions:
OccupiedCore
in a backer bitfield for example. We would need to do some unification of backer bitfield (bitwise OR) because different subsets of backers might appear in different chains and we'd want to request from anyone who signed a statement.The text was updated successfully, but these errors were encountered: