From 4c080a98e714dec21a9a7a7c7c4879b9814d9449 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar <43061995+xenowits@users.noreply.github.com> Date: Mon, 6 Nov 2023 01:50:59 +0530 Subject: [PATCH] update selections endpoint description (#368) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Oisín Kyne <4981644+OisinKyne@users.noreply.github.com> --------- Co-authored-by: Oisín Kyne <4981644+OisinKyne@users.noreply.github.com> --- apis/validator/beacon_committee_selections.yaml | 6 ++++-- apis/validator/sync_committee_selections.yaml | 9 +++++---- 2 files changed, 9 insertions(+), 6 deletions(-) diff --git a/apis/validator/beacon_committee_selections.yaml b/apis/validator/beacon_committee_selections.yaml index c906012e..991b5ee4 100644 --- a/apis/validator/beacon_committee_selections.yaml +++ b/apis/validator/beacon_committee_selections.yaml @@ -5,8 +5,10 @@ post: This endpoint should be used by a validator client running as part of a distributed validator cluster, and is implemented by a distributed validator middleware client. This endpoint is used to exchange partial selection proofs for combined/aggregated selection proofs to allow a validator client - to correctly determine if one of its validators has been selected to perform an aggregation duty in this slot. - Consensus clients need not support this endpoint and may return a 501. + to correctly determine if any of its validators has been selected to perform an attestation aggregation duty in a slot. + Validator clients running in a distributed validator cluster must query this endpoint at the start of an epoch for the current and lookahead (next) epochs for + all validators that have attester duties in the current and lookahead epochs. Consensus clients need not support this + endpoint and may return a 501. tags: - Validator requestBody: diff --git a/apis/validator/sync_committee_selections.yaml b/apis/validator/sync_committee_selections.yaml index 857009fd..a04c3f6a 100644 --- a/apis/validator/sync_committee_selections.yaml +++ b/apis/validator/sync_committee_selections.yaml @@ -5,10 +5,11 @@ post: Submit sync committee selections to a DVT middleware client. It returns the threshold aggregated sync committee selection. This endpoint should be used by a validator client running as part of a distributed validator cluster, and is implemented by a distributed validator middleware client. This endpoint is - used to exchange partial selection proof slot signatures for combined/aggregated selection proofs to - allow a validator client to correctly determine if one of its validators has been selected to perform - a sync committee contribution (sync aggregation) duty in this slot. Consensus clients need not support - this endpoint and may return a 501. + used to exchange partial selection proofs (slot signatures) for combined/aggregated selection proofs to + allow a validator client to correctly determine if any of its validators has been selected to perform a + sync committee contribution (sync aggregation) duty in a slot. Validator clients running in a distributed validator cluster must query this endpoint + at the start of each slot for all validators that are included in the current sync committee. Consensus + clients need not support this endpoint and may return a 501. tags: - Validator requestBody: