Description
System information
On Gnosis, Lighthouse immediately started receiving invalid aggregate attestations after the Electra fork.
May 01 05:07:59.679 DEBG Invalid attestation from network type: "aggregated", peer_id: 16Uiu2HAm6gCRWT3sru64ApYDyML1G1tnVTfdrYxnyNQFYATxwRxS, block: 0xa3821573c8f8b5f31ab9c94ea74caf87177e30e84b0dab712ec4bb7e2dec00d7, reason: BeaconChainError(AttestationValidationError(BeaconStateError(EmptyCommittee)))
So far, I've traced them to Caplin:
Apr 30 16:23:28.715 DEBG Identified Peer protocols: ["/eth2/beacon_chain/req/beacon_blocks_by_range/2/ssz_snappy", "/eth2/beacon_chain/req/beacon_blocks_by_root/2/ssz_snappy", "/eth2/beacon_chain/req/blob_sidecars_by_range/1/ssz_snappy", "/eth2/beacon_chain/req/blob_sidecars_by_root/1/ssz_snappy", "/eth2/beacon_chain/req/goodbye/1/ssz_snappy", "/eth2/beacon_chain/req/light_client_bootstrap/1/ssz_snappy", "/eth2/beacon_chain/req/light_client_finality_update/1/ssz_snappy", "/eth2/beacon_chain/req/light_client_optimistic_update/1/ssz_snappy", "/eth2/beacon_chain/req/light_client_updates_by_range/1/ssz_snappy", "/eth2/beacon_chain/req/metadata/1/ssz_snappy", "/eth2/beacon_chain/req/metadata/2/ssz_snappy", "/eth2/beacon_chain/req/ping/1/ssz_snappy", "/eth2/beacon_chain/req/status/1/ssz_snappy", "/floodsub/1.0.0", "/ipfs/id/1.0.0", "/ipfs/id/push/1.0.0", "/meshsub/1.0.0", "/meshsub/1.1.0"], observed_address: /ip4/95.217.118.126/tcp/9000, listening_addresses: [/ip4/15.235.226.108/tcp/4001], agent_version: erigon/caplin, protocol_version: , peer: 16Uiu2HAm6gCRWT3sru64ApYDyML1G1tnVTfdrYxnyNQFYATxwRxS, service: libp2p
Expected behaviour
Caplin should only set a committee bit in its aggregate attestations if there are attestations from that committee included. I'm going to run a branch with some more debug logs to see exactly how many committee bits Caplin is setting.
Steps to reproduce the behaviour
Backtrace
[backtrace]