lambdaclass / lambdaclass/ethlambda

Don't aggregate proposer signature with attestation proofs

Open
#471 0 comments 0 reactions 1 assignee View on GitHub

@MegaRedHand is already working on this.

Since Jul 15, 2026.

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

Description

We currently aggregate the proposer signature with the rest of the proofs, which is unnecessary: the proposer signature is ~2KB and takes >1ms to verify, so having it travel alongside the block proof adds almost no overhead.

What's more, avoiding the aggregation of it reduces aggregation time by about 50% in the common case of 1 attestation blocks (since we aggregate 1 proof instead of 2, so half the work). It would also make empty blocks trivial to produce and propagate over the network, since they require no aggregation and weigh only as much as the signature plus the block (we assume the block proof is empty when there are no attestations).

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.