Sync committee for a period

curl --request GET \
  --url 'https://beaconcha.in/api/v1/sync_committee/{period}?apikey='

{
  "status": "OK",
  "data": {
    "period": 500,
    "start_epoch": 128000,
    "end_epoch": 128255,
    "validators": [
      383220,
      12142,
      265015,
      260079
    ]
  }
}

Sync Committees

Sync committee for a period

Retrieve the sync committee membership for a given sync period. The sync committee contains 512 validator indices that participate in light-client finality via sync committee signatures. The validators in the response are ordered by the sync-committee index (the position used when interpreting syncaggregate_bits in blocks). A sync period spans 256 consecutive epochs. Sync committees were introduced with the Altair upgrade. Requests for periods before Altair return an error because no sync committee exists for those periods. On Ethereum mainnet, Altair activated at epoch 74240 (period 290).

GET

api

sync_committee

{period}

Sync committee for a period

curl --request GET \
  --url 'https://beaconcha.in/api/v1/sync_committee/{period}?apikey='

{
  "status": "OK",
  "data": {
    "period": 500,
    "start_epoch": 128000,
    "end_epoch": 128255,
    "validators": [
      383220,
      12142,
      265015,
      260079
    ]
  }
}

Authorizations

apikey

string

query

required

Path Parameters

period

required

The sync period to fetch. Provide a non-negative integer period index, or use one of the special tags: latest (current period) or next (the upcoming period if available). Special tags for convenience.

Available options:

latest,

next

Example:

"latest"

Response

The sync committee for the requested period was found. The data object contains the period index, the start and end epochs, and the list of 512 validator indices in committee order.

Standard success envelope used by all API endpoints.

status

enum<string>

HTTP-independent status of the API operation. For successful responses this is always "OK".

Available options:

OK

data

object

Sync committee membership for a single sync period. Includes the period index, the start and end epochs, and the 512 validator indices ordered by sync-committee index. The ordering matches the bit positions in syncaggregate_bits found in blocks.

Show child attributes

data.period

integer

Sync period index (>= 0). Each period spans 256 consecutive epochs.

Required range: x >= 0

Example:

500

data.start_epoch

integer

Epoch at which the sync period begins. On Ethereum mainnet this equals period * 256.

Required range: x >= 0

Example:

128000

data.end_epoch

integer

Epoch at which the sync period ends (inclusive). On Ethereum mainnet this equals start_epoch + 255.

Required range: x >= 0

Example:

128255

data.validators

integer[]

List of validator indices that form the sync committee for this period, ordered by sync-committee index (length 512 as per the consensus spec).

Required array length: 512 elements

Required range: x >= 0

Example:

[383220, 12142, 265015, 260079]

Validator performance leaderboard

Rocket Pool network statistics

Introduction

API Docs

Sync committee for a period

Authorizations

Path Parameters

Response