Skip to main content

post-eth-v1-beacon-pool-sync_committees

POST /eth/v1/beacon/pool/sync_committees

Submit sync committee signatures to node​

Sends objects with the sync committee signature to the node.

Signatures from the sync committee are necessary for Altair networks but are absent from phase 0.

A node MUST broadcast a sync committee signature on all relevant subnets if it has been validated successfully.

The node MUST provide a 400 error including information about which sync committee signatures have failed and why if one or more of them fail validation.

Example Request and Result for /v1/beacon/pool/sync_committees​

In this section, we provide an illustrative example of a request made to retrieve details contents using the /v1/beacon/pool/sync_committees endpoint. Additionally, we present the resulting response containing information about submitting sync committee signatures to node.

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!

Submit sync committee signatures to node​

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

Sync committee signatures are stored in pool and broadcast on
appropriate subnet

Curl Request example​

curl -X 'POST' \
  'https://eth-holesky-beacon.blastapi.io/<project-id>/eth/v1/beacon/pool/sync_committees' \
  -H 'accept: */*' \
  -H 'Content-Type: application/json' \
  -d '[
  {
    "slot": "1",
    "beacon_block_root": "0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2",
    "validator_index": "1",
    "signature": "0x1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505cc411d61252fb6cb3fa0017b679f8bb2305b26a285fa2737f175668d0dff91cc1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505"
  }
]'