Skip to main content

post-eth-v1-validator-beacon_committee_subscriptions

POST /eth/v1/validator/beacon_committee_subscriptions

Beacon node signal to get ready for 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:

  • subscribe to the subnet topic on gossipsub
  • aggregate the attestations obtained on that subnet
info

The beacon node has set up the attestation subnet, and the lot signature is legitimate.

Keep in mind that, for a variety of reasons, we cannot guarantee the Beacon node will locate peers for 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 signal beacon node to get ready for a committee sub net.

Parameters​

  • none
info

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!

Beacon node signal to get ready for committee subnet.​

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

Successful response

Curl Request example​

curl -X 'POST' \
  'https://eth-holesky-beacon.blastapi.io/<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
  }
]'