POST /eth/v1/validator/sync_committee_selections

Find out if a distributed validator has been chosen to contribute to the sync committee.

Send a DVT middleware client the sync committee selections. The threshold aggregated sync committee selection is returned. This endpoint is implemented by a distributed validator middleware client and should be accessed by a validator client operating within a distributed validator cluster. To accurately ascertain whether any of its validators have been chosen to carry out a sync committee contribution (sync aggregation) task in a slot, a validator client can use this API to exchange partial selection proofs (slot signatures) for combined/aggregated selection proofs. In order to find out which validators are a part of the current sync committee, validator clients operating in a distributed validator cluster need to access this endpoint at the beginning of each slot. Consensus clients may return a 501 and are not required to provide this endpoint.

Example Request and Result for /v1/validator/sync_committee_contribution

In this section, we provide an illustrative example of a request made to retrieve details contents using the /v1/validator/sync_committee_contribution endpoint. Additionally, we present the resulting response containing information about if a distributed validator has been chosen to contribute to the sync committee.

Parameters

Fields	String	Description
slot*	string	The slot for which a sync committee contribution should be created.
subcommittee_index*	string	The subcommittee index for which to produce the contribution.
beacon_block_root*	string	The block root for which to produce the contribution.

The example in this section uses a non-existing project id.

Make sure you replace it with your Ethereum Holesky Beacon endpoint when issuing the API calls.

Don't have a project id? Here's a straightforward guide on how to obtain one!

Find out if a distributed validator has been chosen to contribute to the sync committee.

POST https://eth-holesky-beacon.blastapi.io/<project-id>/eth/v1/validator/sync_committee_contribution

Query Parameters

Name	Type	Description
slot*	string	1
subcommittee_index*	string	1
beacon_block_root*	string	0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2

200: OK Expand for a detailed response example

{
  "data": {
    "slot": "1",
    "beacon_block_root": "0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2",
    "subcommittee_index": "1",
    "aggregation_bits": "0xffffffffffffffffffffffffffffffff",
    "signature": "0x1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505cc411d61252fb6cb3fa0017b679f8bb2305b26a285fa2737f175668d0dff91cc1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505"
  }
}

Curl Request example

curl -X 'GET' \
  'https://eth-holesky-beacon.blastapi.io/<project-id>/eth/v1/validator/sync_committee_contribution?slot=1&subcommittee_index=1&beacon_block_root=0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2' \
  -H 'accept: application/json'