Ethereum validator

• 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.

Related

• Shanghai upgrade
• rated.network
• Beacon Chain
• lighthouse validator client (vc)

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
• Staking, Tezos, Cosmos, StakeWise, Staking facilities, Finoa, APR, validator, Ethereum Beacon Chain, Lido Staked ETH, Attestation effectiveness, lighthouse beacon node, Staking rewards, Chorus One, Allnodes, Ethereum SRB, Liquid Staking Token (LST), LPOS, Liquid Staked ETH (LsETH)
• 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

https://launchpad.ethereum.org/en/faq