Improve signature and proof selection algorithm
@MegaRedHand is already working on this.
Since Jul 15, 2026.
Assessment
This issue has not been assessed yet.
Description
We currently follow the spec on the way signatures are selected for aggregation. We should use some custom algorithm prioritizing valuable attestations, in a similar way to how we select attestations in block building.
Also, related to #493, we should prioritize doing an initial round of raw signature aggregation before moving on to recursive proof aggregation.
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lambdaclass/ethlambda
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaclass/ethlambda#529 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#521 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
lambdaclass/ethlambda#609 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lambdaclass/ethlambda#602 ·
-
performance
Difficulty 4/5 3-5 days Newbie friendliness 55/100
lambdaclass/ethlambda#599 · 1 comment ·
All issues in lambdaclass/ethlambda
Similar issues
-
todo:perf
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
ACP agents get no MCP servers when the thread is created before the project's first worktree loads Openstate:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zed-industries/zed#64611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
objectionary/phie#154 ·