lambdaclass / lambdaclass/ethlambda
Signature aggregation optimizations
Open
Nobody has claimed this yet.
performance
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Description
Block building is in a good spot. We should now focus on signature aggregation, which has room left for optimizations.
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.
Research direction
No file, test, benchmark, or specific optimization target is named. Start by locating the Rust code that performs signature aggregation and understand how it is used during block building. Done is an agreed, measured improvement to signature aggregation performance without changing consensus behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100