Skip to content

Commit

Permalink
update selections endpoint description (#6)
Browse files Browse the repository at this point in the history
* edit api descriptions

* cleanup

* edit message
  • Loading branch information
xenowits authored Jul 5, 2023
1 parent e46bd0c commit 9e8f228
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 5 deletions.
5 changes: 3 additions & 2 deletions apis/validator/beacon_committee_selections.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
7 changes: 4 additions & 3 deletions apis/validator/sync_committee_selections.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down

0 comments on commit 9e8f228

Please sign in to comment.