Solia saysTo become a validator: lock 32 ETH in the deposit contract, then wait in the activation queue — limited by a churn rate of max(4, active/65536) per epoch.
The deposit contract is an immutable execution-layer contract that takes 32 ETH and a validator public key. Once your deposit is included, you enter the activation queue. The beacon chain caps how fast new validators come online via the churn limit: max(4, active/65536) per epoch — about 8 activations per epoch at the current ~1M active set.
The cap protects consensus stability: an attacker cannot bulk-activate millions of validators in one epoch and overwhelm the existing set. The cost is that during demand spikes the activation queue can stretch to weeks. The demo computes the time to drain a 100,000-deep queue.
Power-ups you unlock
32 ETH deposit on the execution-layer deposit contract
Activation queue limited by churn = max(4, active/65536) per epoch
At 1M active validators ≈ 8 activations / epoch
Queue protects against bulk-activation attacks
Big queues stretch to weeks during high demand
The Reentrancy Reaper attacks — common mistakes
Sending less or more than 32 ETH (deposits round to 32)
Assuming activation is instant after the deposit
Forgetting BLS withdrawal credentials differ from execution-layer addresses
Underestimating the queue depth during demand spikes
Boss battleFor a 100,000-deep activation queue and a churn of 8/epoch, compute the days needed to drain it.