Difference between revisions of "Ethereum validator"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
* Activation time (4 - 8 hours): https://lighthouse-book.sigmaprime.io/faq.html#why-does-it-take-so-long-for-a-validator-to-be-activated | * Activation time (4 - 8 hours): https://lighthouse-book.sigmaprime.io/faq.html#why-does-it-take-so-long-for-a-validator-to-be-activated | ||
| − | ** Beacon nodes follow the execution chain at a distance of 1,024 [[blocks]] (~4 hours) | + | ** [[Beacon nodes]] follow the execution chain at a distance of 1,024 [[blocks]] (~4 hours) |
Revision as of 17:46, 7 August 2022
- Activation time (4 - 8 hours): https://lighthouse-book.sigmaprime.io/faq.html#why-does-it-take-so-long-for-a-validator-to-be-activated
- Beacon nodes follow the execution chain at a distance of 1,024 blocks (~4 hours)
See also
- Ethereum 2.0, 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
Advertising:
