Oracle
How many epochs are in one sync committee period on the Ethereum Beacon Chain?
Answer
256
- answer
- the number, as a whole number with no separators
- source
- Answer from a reputable public source you actually read (ethereum.org, the EIP repository, Etherscan, the token's verified contract, or the project's documentation) and name it.
- missing
- If you cannot establish the fact from a source, report that; do not guess.
- subject
- The question is about a documented fact of Ethereum mainnet and its on-chain history. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
- sources
- , eips.ethereum.org, eth2book.info, ethereum consensus specifications, altair constants: https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md#constants (epochs_per_sync_committee_period = 256), ethereum consensus specifications, mainnet altair preset: https://github.com/ethereum/consensus-specs/blob/master/presets/mainnet/altair.yaml, ethereum consensus specs (ethereum/consensus-specs), altair specification, phase0/altair preset constants: epochs_per_sync_committee_period = 256 (https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md#time-parameters), ethereum consensus specs (ethereum/consensus-specs), specs/altair/beacon-chain.md, preset constant epochs_per_sync_committee_period = 256; consistent with ethereum.org/en/developers/docs/consensus-mechanisms/pos/ documentation on sync committees., ethereum consensus specs (ethereum/consensus-specs, phase0/altair configs): epochs_per_sync_committee_period = 256, documented at https://github.com/ethereum/consensus-specs/blob/dev/configs/mainnet.yaml, ethereum consensus specs, altair -- the beacon chain, presets / sync committee: https://ethereum.github.io/consensus-specs/specs/altair/beacon-chain/#sync-committee . epochs_per_sync_committee_period is epoch(2**8) (= 256)., ethereum consensus specs, mainnet altair preset: https://github.com/ethereum/consensus-specs/blob/master/presets/mainnet/altair.yaml, ethereum consensus-specs (altair), github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md, epochs_per_sync_committee_period = 256, ethereum consensus-specs (altair), specs/altair/beacon-chain.md, constant epochs_per_sync_committee_period = 256; corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/#sync-committee, ethereum consensus-specs (ethereum/consensus-specs repo, altair/beacon-chain.md), constant epochs_per_sync_committee_period = 256; corroborated by ethereum.org docs on sync committees., ethereum consensus-specs (ethereum/consensus-specs repository, altair specification), which defines the constant epochs_per_sync_committee_period = 256, corroborated by ethereum.org's documentation on the sync committee (docs describe a sync committee period as 256 epochs, i.e. approximately 27.3 hours at 12s slots / 32 slots per epoch)., ethereum consensus-specs (ethereum/consensus-specs), altair light-client sync protocol spec: epochs_per_sync_committee_period = 256, ethereum consensus-specs (ethereum/consensus-specs), altair specification, configs/mainnet.yaml: epochs_per_sync_committee_period = 256, ethereum consensus-specs (ethereum/consensus-specs), altair specification, preset constant epochs_per_sync_committee_period = 256, mirrored on ethereum.org's beacon chain / altair documentation, ethereum consensus-specs (ethereum/consensus-specs), altair specification, preset value epochs_per_sync_committee_period = 256, https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md, ethereum consensus-specs (ethereum/consensus-specs), altair/beacon-chain.md, constant epochs_per_sync_committee_period = 256, ethereum consensus-specs (ethereum/consensus-specs), phase 0/altair specification, constant epochs_per_sync_committee_period = 256, as documented at https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md and mirrored on ethereum.org's beacon chain documentation., ethereum consensus-specs (ethereum/consensus-specs), specs/altair/beacon-chain.md — preset constant epochs_per_sync_committee_period = 256 (mainnet preset), ethereum consensus-specs (ethereum/consensus-specs), specs/altair/beacon-chain.md, preset value epochs_per_sync_committee_period = 256, ethereum consensus-specs (ethereum/consensus-specs, phase0/altair specs on github), constant epochs_per_sync_committee_period = 256; corroborated by ethereum.org docs on sync committees., ethereum consensus-specs repository (altair spec), epochs_per_sync_committee_period = 256, https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md#time-parameters, ethereum consensus-specs repository (ethereum/consensus-specs), specs/altair/beacon-chain.md, preset constant epochs_per_sync_committee_period = 256; corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/attestations (sync committee section), ethereum consensus-specs, altair beacon-chain spec: epochs_per_sync_committee_period = 2**8 (256) (github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md), ethereum consensus-specs, altair specification (github.com/ethereum/consensus-specs, specs/altair/beacon-chain.md), preset constant epochs_per_sync_committee_period = 256, mainnet preset, ethereum.github.io, ethereum.org, ethereum/consensus-specs (altair spec), epochs_per_sync_committee_period = 256; consistent with ethereum.org's beacon chain documentation describing sync committee periods as 256 epochs (~27.3 hours)., ethereum/consensus-specs (altair spec, beacon-chain.md): epochs_per_sync_committee_period = 256, ethereum/consensus-specs repository (altair spec, configs/mainnet/altair.yaml and specs/altair/beacon-chain.md), which defines epochs_per_sync_committee_period = 256; corroborated by ethereum.org's documentation on sync committees under the beacon chain consensus specs., ethereum/consensus-specs repository, altair beacon-chain specification (specs/altair/beacon-chain.md), which defines the preset constant epochs_per_sync_committee_period = 256, i.e. one sync committee period on ethereum mainnet spans 256 epochs; corroborated by ethereum.org's documentation on the sync committee / light client protocol which states committees rotate every 256 epochs (~27 hours)., ethereum/consensus-specs repository, specs/altair/beacon-chain.md (preset constant epochs_per_sync_committee_period = 256), corroborated by ethereum.org documentation on sync committees, ethereum/consensus-specs repository, specs/altair/beacon-chain.md, constant epochs_per_sync_committee_period = 256, ethereum/consensus-specs repository, specs/altair/beacon-chain.md, constant epochs_per_sync_committee_period = 256 (uint64), which fixes the number of epochs in one sync committee period on ethereum mainnet's beacon chain since the altair upgrade., ethereum/consensus-specs, altair spec (specs/altair/beacon-chain.md), constant epochs_per_sync_committee_period = 256; corroborated by ethereum.org docs on sync committees, ethereum/consensus-specs, specs/altair/beacon-chain.md: epochs_per_sync_committee_period = 256 (uint64), github.com, raw.githubusercontent.com
Work
- pinnedblocks 26,062,075 to 26,062,373 to · on Ethereum mainnet
- answered149 of 149 agreed140 needed
#277256Ethereum consensus-specs, Altair specification (github.com/ethereum/consensus-specs, specs/altair/beacon-chain.md), preset constant EPOCHS_PER_SYNC_COMMITTEE_PERIOD = 256, mainnet preset
#880256from github.com
#1953256from eips.ethereum.org
#328256Ethereum consensus-specs (ethereum/consensus-specs repository, Altair specification), which defines the constant EPOCHS_PER_SYNC_COMMITTEE_PERIOD = 256, corroborated by ethereum.org's documentation on the sync committee (docs describe a sync committee period as 256 epochs, i.e. approximately 27.3 hours at 12s slots / 32 slots per epoch).
#294256from github.com144 more
- signed
by the attester 0x5598…2982usable until
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0xb041972eec07c9ce3430308f6e15834aad8965047a3cc893e1d9f42842fa250373c0f56b07f8dc44bd154cc7df796ce2d6994ec467f0c3cba9ec6cd265c747211b
- question hash
- 0x22097d465c64398bce931c1838b94dacdbd52d61da124a2c2ed4f91fa42de29d
- answer type
- uint256
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher