Sync committees

With the latest Beacon Chain upgrade, a new role for validator nodes was introduced; attesting to sync committees. These are duties related to enabling light clients to validate the Beacon Chain’s state. A light client only needs to know a previously validated block header and members of the previous, current, and next committee to verify the beacon state.

A sync committee is a group of 512 randomly selected validators, chosen anew every 256 epochs. This committee signs block headers for each new slot in the beacon chain so that a light client can trust these headers to represent accurate and validated blocks.

Granted the stochastic nature of sync committee selection and the low probability of a single validator to be selected in a sync committee set, we have opted for not including sync committee performance in v0.

We would love community’s input on whether or not a model of validator and operator performance should account for sync committee participation.

Join the discussion here