target sync committee aggregators to 16 #2514
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@mcdee Did some quick math to show that the current configuration of
TARGET_AGGREGATORS_PER_SYNC_SUBCOMMITTEE
as4
had an unacceptably high probability of sync committee subnets not having aggregators.@hwwhww tossed the math and some options into this spreadsheet. Based on discussions, it looks like the choice of
16
is the right tradeoff to generally have a high chance of having at least one aggregator per slot, even on a daily basis.Note, that
4
was naively selected to reduce chatter on yet another global channel, but assuming attestation aggregation is not already overwhelming, this increases global messages for ~6% (4 more 16 aggregator topics on top of the 64 attestation topics that also have 16 aggregator targets)