DVT Compatibility

[AgeManning]

Description

There are two endpoints in the beaconapi specs, specifically designed for DVT middleware:

• https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Validator/submitBeaconCommitteeSelections
• https://ethereum.github.io/beacon-APIs/?urls.primaryName=dev#/Validator/submitSyncCommitteeSelections

We have a --distributed flag in the VC now. We should implement these endpoints on the BN and when this flag is set on the VC use these endpoints.

There is further information and testing links in this comment: #4867 (comment)

[michaelsproul]

My understanding is that we do not need to implement these on the BN: just to use them from the VC.

[michaelsproul]

I will investigate

[OisinKyne]

My understanding is that we do not need to implement these on the BN: just to use them from the VC.

Correct. You just need to call them with the VC, charon returns an aggregated signature in exchange for the partial one sent, and then the aggregation selection process continues as normal from there :)