-
Notifications
You must be signed in to change notification settings - Fork 140
Open
Labels
Description
After Alan fork the responsibilities of AttesterHandler became super unintuitive, while debugging some misbehaving duties I figured out that it roughly does this:
- fetches attestation & aggregation duties that will eventually be processed by
CommitteeRunnerandAggregatorRunnerrespectively, and yet on top of that we haveCommitteeHandlerthat also doing some processing (but not fetching, it relies onAttesterHandler, and maybeSyncCommitteeHandler, to fetch the duties I guess) - performs some preliminary steps for Aggregation duty, as I previously documented here
It is pretty confusing to navigate the code AttesterHandler is involved in + it prevents us from instrumenting the AttesterHandler code with committee-related nomenclature (to be able to get the full duty trace from start to finish),
What we want to do instead is to split duty fetching & handling by their respective roles in clean manner.