POST /eth/v1/validator/beacon_committee_subscriptions

Signal beacon node to prepare for a committee subnet

When the beacon node receives this request, use discv5 to look for peers connected to this subnet. If needed, replace the current peers with those peers. If beacon node is_aggregator, validator needs to:

  • announce subnet topic subscription on gossipsub

  • aggregate attestations received on that subnet

Example Request and Result for /v1/validator/beacon_committee_subscriptions

In this section, we provide an illustrative example of a request made to retrieve details contents using the /v1/validator/beacon_committee_subscriptions endpoint. Additionally, we present the resulting response containing information about preparing the beacon node for a committee subnet.


  • none

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!

Signal beacon node to prepare for a committee subnet


Slot signature is valid and beacon node has prepared the attestation subnet.
Note that we cannot be certain the Beacon node will find peers for that subnet for various reasons.

Curl Request example

curl -X 'POST' \
  '<project-id>/eth/v1/validator/beacon_committee_subscriptions' \
  -H 'accept: */*' \
  -H 'Content-Type: application/json' \
  -d '[
    "validator_index": "1",
    "committee_index": "1",
    "committees_at_slot": "1",
    "slot": "1",
    "is_aggregator": true

Last updated