Skip to content

VC sends multiple submit attestation requests #7838

@KaloyanTanev

Description

@KaloyanTanev

Describe the bug
Post-electra committee index was taken outside of the signed attestation data. Beacon API requests were modified and now VCs managing multiple keys do need to send only 1 request to /eth/v1/validator/attestation_data for all of its keys, specifying committee_index as 0. Respectively we also expect only 1 call with all of the signed attestations to /eth/v2/beacon/pool/attestations.

Currently Nimbus VC sends multiple signed attestation requests to the beacon node. While this is not incorrect per se, it creates bigger overhead in cases with many keys. In our situation of distributed validators, this is even more prominent, as each of those signatures is a partial signature and the distributed validator needs to propagate this to the other distributed validator nodes.

To Reproduce
Applicable to any Nimbus VC with high enough amount of keys that multiple keys need to attest in a slot.

Screenshots
Adding screenshots of comparison between Nimbus VC's /eth/v2/beacon/pool/attestations requests and another VC in a DV cluster with close to 2000 active keys.

Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions