Pipeline recursive aggregation with other validator duties

Open
#583 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
blockchain

Research direction

Trace the existing aggregation-period worker and the scheduling logic for proposal duties. Determine how the worker can remain active outside aggregation periods and pause during proposal duties; done means aggregation continues whenever proposal duties are absent and is paused while they are active.

Written by the indexing model from the issue text.

Description

performance

We currently aggregate signatures and payloads only during the aggregation period. We should instead try to do as much aggregation as possible during slots where we don't have proposal duties. In order to achieve this, we can have an aggregation worker always live, pausing it only whenever we have proposal duties.

Dominant language
Rust
Stars
82
Forks
28
Avg merge
1d 20h
Merged PRs (30d)
20

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethlambda

All issues in lambdaclass/ethlambda

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.