Difference between revisions of "Ethereum validator"
Jump to navigation
Jump to search
↑ https://launchpad.ethereum.org/en/faq
Line 2: | Line 2: | ||
* 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) | ||
− | ** ETH1_VOTING_PERIOD is defined as 32 [[epochs]] (~3.4 hours) | + | ** <code>ETH1_VOTING_PERIOD</code> is defined as 32 [[epochs]] (~3.4 hours) |
Revision as of 14:17, 10 May 2023
- 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)
ETH1_VOTING_PERIOD
is defined as 32 epochs (~3.4 hours)
- MAX_EFFECTIVE_BALANCE: 32 ETH on mainnet, usually 3.2 ETH on testnets
There is no advantage to having more than 32 ETH staked. [1]
Clients
Related
See also
- Validator, Ethereum validator, Validator effectiveness, Agoric validator, Attestation Reward Scale, Attestation aggregation, Validator key, Slashed, SSV, Distributed validators, Fee recipient, Validator index, Proposer
- 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
Advertising: