From 9e8f228379b9ecda86c35eea1944a9d1c769da56 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar <43061995+xenowits@users.noreply.github.com> Date: Wed, 5 Jul 2023 15:17:16 +0530 Subject: [PATCH 1/2] update selections endpoint description (#6) * edit api descriptions * cleanup * edit message --- apis/validator/beacon_committee_selections.yaml | 5 +++-- apis/validator/sync_committee_selections.yaml | 7 ++++--- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/apis/validator/beacon_committee_selections.yaml b/apis/validator/beacon_committee_selections.yaml index c906012e..333ba787 100644 --- a/apis/validator/beacon_committee_selections.yaml +++ b/apis/validator/beacon_committee_selections.yaml @@ -5,8 +5,9 @@ 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 one of its validators has been selected to perform an aggregation duty in a slot. + Validator clients must query this endpoint at the start of an epoch for all validators that have attester duties + in that epoch. 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..176bb6f6 100644 --- a/apis/validator/sync_committee_selections.yaml +++ b/apis/validator/sync_committee_selections.yaml @@ -6,9 +6,10 @@ post: 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. + 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 a slot. Validator clients must query this endpoint + at the start of an epoch for all validators that have sync committee contribution duties in that epoch. + Consensus clients need not support this endpoint and may return a 501. tags: - Validator requestBody: From 453b01ee713b6630dcee6d99b7e528d6b2918a11 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar <43061995+xenowits@users.noreply.github.com> Date: Tue, 17 Oct 2023 12:01:30 +0000 Subject: [PATCH 2/2] add lookahead epochs (#7) * update to mention lookahead epochs * clarify current and lookahead epochs * review comments --- apis/validator/beacon_committee_selections.yaml | 7 ++++--- apis/validator/sync_committee_selections.yaml | 8 ++++---- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/apis/validator/beacon_committee_selections.yaml b/apis/validator/beacon_committee_selections.yaml index 333ba787..5bb0e52d 100644 --- a/apis/validator/beacon_committee_selections.yaml +++ b/apis/validator/beacon_committee_selections.yaml @@ -5,9 +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 a slot. - Validator clients must query this endpoint at the start of an epoch for all validators that have attester duties - in that epoch. 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 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 176bb6f6..0a6a80cd 100644 --- a/apis/validator/sync_committee_selections.yaml +++ b/apis/validator/sync_committee_selections.yaml @@ -5,11 +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 + 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 must query this endpoint - at the start of an epoch for all validators that have sync committee contribution duties in that epoch. - Consensus clients need not support this endpoint and may return a 501. + 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: