[WIP] Committee aggregation #282

kamilsa · 2026-01-14T12:38:27Z

🗒️ Description

Introduces aggregator role and subnet aggregation.

Every validator is assigned to one of the attestation subnets
Aggregators collect signatures that correspond to validators from their subnet
* If aggregators collected 90% of signatures from their subnet by the beginning of slot 2, they produce aggregated attestation and propagate it into aggregation topic
Validators subscribe to aggregation topic, so that next block proposer may include committee aggregations into the block (without recursive aggregation for now)

Interval	Devnet 2	Devnet 3
0	Aggregate signatures and put proofs into the block	Put collected subnet proofs into the block
1	Cast a vote and publish to attestation topic	Cast a vote and publish to attestation topic + publish to attestation_{subnet_id} topic
2	Update safe target	Update safe target. Aggregator: aggregate collected signatures and broadcast a subnet proof into the aggregation topic
3	Attestations accepted	Attestations accepted

Remaining work

~~- [ ] Process the case when aggregators did not observe enough signatures by the beginning of interval 2~~
- [ ] Add predicates for gossipsub propagations of aggregated signatures (e.g. do not propagate aggregation if we already observed the one for the same committee, but proving more validators signatures) Not needed for now as we have only a single aggregator per committee, so only one aggregation

Update to latest master

🔗 Related Issues or PRs

leanEthereum/pm#56
leanEthereum/pm#58

✅ Checklist

Ran tox checks to avoid unnecessary CI fails:
```
uvx tox
```
Considered adding appropriate tests for the changes (will add in a separate PR)
Considered updating the online docs in the ./docs/ directory.

use committee aggregated signature proofs

also rename gossip_signatures to gossip_committee_signatures

jihoonsong

Great work! Please excuse leaving some comments while it's still in draft. Just wanted to help iterate faster :)

docs/client/validator.md

jihoonsong · 2026-01-14T15:25:40Z

src/lean_spec/subspecs/containers/state/state.py

        # Configure the genesis state.
        genesis_config = Config(
            genesis_time=genesis_time,
+            attestation_subnet_count=AGGREGATION_COMMITTEE_COUNT,


I admit that I was the one who advocated for attestation committee, but based on the fact that validators only push their attestations to aggregators in their subnet without subscribing to it, I now think aggregation committee gives us slightly better description.

I don't mind whichever we choose—either attestation committee or aggregation committee—but I do think we need to stick to one thing consistently in the Lean spec and pq-devnet-3.md in the pm repo.

I don't have a strong preference too, however I think the rationale for topic names in beacon chain spec is based on the type of messages that are being propagated to this topic. For consistency we should probably stick to the same logic and keep using attestation subnets and attestation committees

Sounds great! In the same vein, what do you think about this one?

looks good to me, applied your suggestion

src/lean_spec/subspecs/forkchoice/store.py

…ted references

# Conflicts: # src/lean_spec/subspecs/forkchoice/store.py # src/lean_spec/subspecs/networking/__init__.py

src/lean_spec/subspecs/networking/gossipsub/topic.py

docs/client/validator.md

jihoonsong · 2026-01-15T11:42:53Z

docs/client/validator.md

-
-When aggregation is added, aggregators will collect attestations and combine them.
-Aggregated attestations will be broadcast separately.
+Devnet-2 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.


Suggested change

Devnet-2 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.

Devnet-3 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.

…nt in configuration

Aggregate during interval 2 if more threshold signatures were received

g11tech · 2026-01-21T09:45:54Z

docs/client/validator.md

+
+In the devnet-3 design, however, there is one global subnet for signed 
+attestations propagation, in addition to publishing into per committee subnets.
+This is due to 3SF-mini consensus design, that requires 2/3+ of all 


this global bit is not required, once the aggregtors publish signed attestations in the 2nd interval, they can be imported by all validators in the 3rd interval

Unfortunately, without global topic for attestations, we might not be able to receive proofs in time to update safe target during interval 2:

Interval 0: block propagation

Interval 1: votes propagation

Interval 2: signatures aggregation (up to one second for 1000 validators in subnet with 1000sigs/second expected sigs aggregation rate) + proof distribution => No time for updating safe target => in next slot validator votes for old target

src/lean_spec/subspecs/chain/config.py

g11tech · 2026-01-21T10:20:53Z

src/lean_spec/subspecs/containers/attestation/attestation.py

            for data, validator_ids in data_to_validator_ids.items()
        ]
+
+class SignedAggregatedAttestation(Container):


@anshalshukla / @GrapeBaBa do we already have this type?

also better to use message, signature terminlogy

I think we also need aggregated bit vector here as well,

I think we also need aggregated bit vector here as well,

AggregatedSignatureProof contains AggregationBits

@anshalshukla / @GrapeBaBa do we already have this type?

no

This reverts commit 3115ef5.

This reverts commit 9174f5b.

…ttee_count in configuration" This reverts commit 3477d6e.

This reverts commit 6556e81.

GrapeBaBa · 2026-01-27T03:38:49Z

docs/client/networking.md

+
+| Topic Name                                                 | Message Type                | Encoding     |
+|------------------------------------------------------------|-----------------------------|--------------|
+| /lean/consensus/devnet3/blocks/ssz_snappy                  | SignedBlockWithAttestation  | SSZ + Snappy |


original prefix is /leanconsensus, this is an expected change /lean/consensus?

no.
Thanks for noticing. Fixed

# Conflicts: # src/lean_spec/subspecs/chain/config.py # src/lean_spec/subspecs/containers/state/state.py

kamilsa added 14 commits January 13, 2026 09:47

networking: update committee docs

b5b6d8a

networking: add committee size configuration

4867d7d

store committee attestations

7bcedca

Add aggregation in 2nd interval

980b5e8

Committee aggregation

60468af

Rename aggregation committee size to count for clarity

213504a

Remove committee signatures

4fac983

Refactor build_block:

f2651d8

use committee aggregated signature proofs

Clarify attestation broadcasting and update Devnet reference

cc7548c

remove adding proposer signatures to gossip_signatures

cb1a21b

also rename gossip_signatures to gossip_committee_signatures

Refactor subnet ID computation and rename committee signatures variable

e398823

Store proposer signature if same subnet

90fc114

Update build block with selecting aggregations

cdae6a4

Uncomment on_attestation during on_gossip_aggregation

b24d3ed

kamilsa mentioned this pull request Jan 14, 2026

PQ Interop #22 | Jan 14, 2026 ethereum/pm#1866

Closed

Update gossipsub topic names to reflect devnet3

5c952ff

jihoonsong reviewed Jan 14, 2026

View reviewed changes

kamilsa added 2 commits January 15, 2026 16:13

Rename aggregation committee to attestation committee and update rela…

8a0c121

…ted references

Merge remote-tracking branch 'origin/main' into committee-aggregation

cb952f8

# Conflicts: # src/lean_spec/subspecs/forkchoice/store.py # src/lean_spec/subspecs/networking/__init__.py

jihoonsong reviewed Jan 15, 2026

View reviewed changes

kamilsa added 6 commits January 15, 2026 19:59

refactor: rename committee aggregation topic to aggregated attestation

9d721bd

update validator.md to clarify subnet usage in attestation committees

baddbeb

feat: add threshold ratio for committee signature aggregation

6556e81

feat: replace attestation_subnet_count with attestation_committee_cou…

3477d6e

…nt in configuration

feat: add committee signature threshold ratio chain config

9174f5b

feat: aggregate on gossip

3115ef5

Aggregate during interval 2 if more threshold signatures were received

g11tech reviewed Jan 21, 2026

View reviewed changes

src/lean_spec/subspecs/chain/config.py Outdated Show resolved Hide resolved

g11tech reviewed Jan 21, 2026

View reviewed changes

docs: clarify aggregator role in validator participation

3fffe71

unnawut added the specs Scope: Changes to the specifications label Jan 23, 2026

unnawut added this to the pq-devnet-3 milestone Jan 23, 2026

kamilsa added 4 commits January 23, 2026 10:36

Revert "feat: aggregate on gossip"

d0462aa

This reverts commit 3115ef5.

Revert "feat: add committee signature threshold ratio chain config"

e2fd644

This reverts commit 9174f5b.

Revert "feat: replace attestation_subnet_count with attestation_commi…

d40199c

…ttee_count in configuration" This reverts commit 3477d6e.

Revert "feat: add threshold ratio for committee signature aggregation"

d46dd08

This reverts commit 6556e81.

GrapeBaBa reviewed Jan 27, 2026

View reviewed changes

kamilsa added 12 commits January 27, 2026 10:49

Merge remote-tracking branch 'origin/main' into committee-aggregation

2439177

# Conflicts: # src/lean_spec/subspecs/chain/config.py # src/lean_spec/subspecs/containers/state/state.py

refactor: update current_validator_id type from Uint64 to ValidatorIndex

61b8100

Fix tests

d66dfd3

refactor: remove attestation_subnet_count from configuration

360bfb0

Fix tests after attestation_subnet_count from Config

379ddd6

Add validator_id to store & fix tests

fe8317c

rrely on aggregated payloads for block production

6af933b

Fix uvx tox

2b68c0c

Small fixes

22bd960

Fix ci: refactor attestation handling for block construction

7cf9773

Fix ci

6e85356

Fix ci

da21184

	Devnet-2 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.
	Devnet-3 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.

[WIP] Committee aggregation #282

Are you sure you want to change the base?

[WIP] Committee aggregation #282

Conversation

kamilsa commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🗒️ Description

Remaining work

🔗 Related Issues or PRs

✅ Checklist

Uh oh!

jihoonsong left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

g11tech Jan 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

kamilsa commented Jan 14, 2026 •

edited

Loading

g11tech Jan 21, 2026 •

edited

Loading