Submit sync committee signatures to node

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/eth/v1/beacon/pool/sync_committees

Request

Base URL: http://public-mainnet-node.ethereum.org
URL: http://public-mainnet-node.ethereum.org/eth/v1/beacon/pool/sync_committees
Auth: none declared

Request body

slotstring

beacon_block_rootstring hex

validator_indexstring

signaturestring hex

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

Changes

No recorded changes to this operation across all 1 revision of this API.