From 7a1d439b746d70d33e6f5c0dafac16f4a915e276 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Tue, 10 Oct 2023 20:42:18 +0530 Subject: [PATCH 1/3] update to mention lookahead epochs --- apis/validator/beacon_committee_selections.yaml | 4 ++-- apis/validator/sync_committee_selections.yaml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/apis/validator/beacon_committee_selections.yaml b/apis/validator/beacon_committee_selections.yaml index 333ba787..9b6dafe9 100644 --- a/apis/validator/beacon_committee_selections.yaml +++ b/apis/validator/beacon_committee_selections.yaml @@ -6,8 +6,8 @@ post: 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. + Validator clients must query this endpoint at the start of an epoch for the lookahead epochs (current and next epochs) for + all validators that have attester duties in the 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..fed83f49 100644 --- a/apis/validator/sync_committee_selections.yaml +++ b/apis/validator/sync_committee_selections.yaml @@ -8,8 +8,8 @@ post: 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 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 an epoch for the lookahead epochs (current and next epochs) for for all validators that have + sync committee contribution duties in the lookahead epochs. Consensus clients need not support this endpoint and may return a 501. tags: - Validator requestBody: From ab8e4da24d220b348bf6e866864da1f5584c9ba4 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Wed, 11 Oct 2023 12:49:30 +0530 Subject: [PATCH 2/3] clarify current and lookahead epochs --- apis/validator/beacon_committee_selections.yaml | 5 +++-- apis/validator/sync_committee_selections.yaml | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/apis/validator/beacon_committee_selections.yaml b/apis/validator/beacon_committee_selections.yaml index 9b6dafe9..8b56b711 100644 --- a/apis/validator/beacon_committee_selections.yaml +++ b/apis/validator/beacon_committee_selections.yaml @@ -6,8 +6,9 @@ post: 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 the lookahead epochs (current and next epochs) for - all validators that have attester duties in the lookahead epochs. Consensus clients need not support this endpoint and may return a 501. + 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 fed83f49..453adbfa 100644 --- a/apis/validator/sync_committee_selections.yaml +++ b/apis/validator/sync_committee_selections.yaml @@ -8,8 +8,9 @@ post: 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 a slot. Validator clients must query this endpoint - at the start of an epoch for the lookahead epochs (current and next epochs) for for all validators that have - sync committee contribution duties in the lookahead epochs. Consensus clients need not support this endpoint and may return a 501. + at the start of an epoch for the current and lookahead (next) epochs for all validators that have + sync committee contribution duties in the current and lookahead epochs. Consensus clients need not support this + endpoint and may return a 501. tags: - Validator requestBody: From e2b03c580145cf5d32a5093ab77e6a50e1436802 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Mon, 16 Oct 2023 12:41:00 +0530 Subject: [PATCH 3/3] review comments --- apis/validator/beacon_committee_selections.yaml | 2 +- apis/validator/sync_committee_selections.yaml | 9 ++++----- 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/apis/validator/beacon_committee_selections.yaml b/apis/validator/beacon_committee_selections.yaml index 8b56b711..5bb0e52d 100644 --- a/apis/validator/beacon_committee_selections.yaml +++ b/apis/validator/beacon_committee_selections.yaml @@ -5,7 +5,7 @@ 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. + 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. diff --git a/apis/validator/sync_committee_selections.yaml b/apis/validator/sync_committee_selections.yaml index 453adbfa..0a6a80cd 100644 --- a/apis/validator/sync_committee_selections.yaml +++ b/apis/validator/sync_committee_selections.yaml @@ -5,12 +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 the current and lookahead (next) epochs for all validators that have - sync committee contribution duties in the current and lookahead epochs. 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: