Sign in

v1

latestOpenAPI 3.1.02026-07-2612501.4 MB

PostBeaconPoolSyncCommittees

Submits sync committee signature objects to the node.

Sync committee signatures are not present in phase0, but are required for Altair networks.

If a sync committee signature is validated successfully the node MUST publish that sync committee signature on all applicable subnets.

If one or more sync committee signatures fail validation the node MUST return a 400 error with details of which sync committee signatures have failed, and why.

post/{apiKey}/eth/v1/beacon/pool/sync_committees

Path parameters

apiKeystring required
<style> .custom-style { color: #048FF4; } </style>

For higher throughput, please <span class="custom-style"><a href="../docs/quick-start-guide#-creating-your-api-key-on-the-zan-platform" target="_blank">create your own API key</a></span>.

Request body

slotstring required
beacon_block_rootstring hex required
validator_indexstring required
signaturestring hex required

Example request

[
  {
    "slot": "1",
    "beacon_block_root": "0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2",
    "validator_index": "1",
    "signature": "0x1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505cc411d61252fb6cb3fa0017b679f8bb2305b26a285fa2737f175668d0dff91cc1b66ac1fb663c9bc59509846d6ec05345bd908eda73e670af888da41af171505"
  }
]

Response

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