Skip to content

add lookahead epochs #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xenowits merged 3 commits into from
Oct 17, 2023
Merged

add lookahead epochs #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7a1d439
update to mention lookahead epochs
xenowits Oct 10, 2023
ab8e4da
clarify current and lookahead epochs
xenowits Oct 11, 2023
e2b03c5
review comments
xenowits Oct 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions apis/validator/beacon_committee_selections.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
8 changes: 4 additions & 4 deletions apis/validator/sync_committee_selections.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down