Epoch

• Validator activation epoch
• Slot / Slots

lighthouse
--builder-fallback-epochs-since-finalization <builder-fallback-epochs-since-finalization>
          If this node is proposing a block and the chain has not finalized within this number of epochs, it will NOT
          query any connected builders, and will use the local execution engine for payload construction. Setting this
          value to anything less than 2 will cause the node to NEVER query connected builders. Setting it to 2 will
          cause this condition to be hit if there are skips slots at the start of an epoch, right before this node is
          set to propose. [default: 3]
--builder-fallback-skips <builder-fallback-skips>
          If this node is proposing a block and has seen this number of skip slots on the canonical chain in a row, it
          will NOT query any connected builders, and will use the local execution engine for payload construction.
          [default: 3]
--builder-fallback-skips-per-epoch <builder-fallback-skips-per-epoch>
          If this node is proposing a block and has seen this number of skip slots on the canonical chain in the past
          `SLOTS_PER_EPOCH`, it will NOT query any connected builders, and will use the local execution engine for
          payload construction. [default: 8]

See also

• Ethereum 2.0, API, Ethereum tasks, Beacon Chain, Ethereum Staking, validator, Consensus clients, Execution clients, Validation clients, Mainnet, testnets: Prater, Goerli ETH, Inclusion distance, Ethereum attestation, Attestation effectiveness, Attestation Reward Scale, slot, Ethereum upgrades: The Merge, Epoch, Slots, rETH, sETH, stETH, Lido Staked ETH, faucet, Ethereum ports, Subjectivity, Lido Staked ETH, ENR, Sharding, Ethers.js, Yellow paper, synchronization, ECFSDS