lambdaclass / lambdaclass/ethlambda
Improve signature and proof selection algorithm
Open
@MegaRedHand is already working on this.
Since Jul 15, 2026.
performance
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
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.
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.
Assessment
This issue has not been assessed yet.