Difference between revisions of "Ethereum validator"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
** ETH1_VOTING_PERIOD is defined as 32 [[epochs]] (~3.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]] | ||
| + | |||
== See also == | == See also == | ||
* {{eth2}} | * {{eth2}} | ||
[[Category:Ethereum]] | [[Category:Ethereum]] | ||
Revision as of 17:48, 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)
- ETH1_VOTING_PERIOD is defined as 32 epochs (~3.4 hours)
- MAX_EFFECTIVE_BALANCE: 32 ETH on mainnet, usually 3.2 ETH on testnets
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:
