validator exit queue
The validator exit queue is a rate limiter on how quickly validators may leave (or join) Ethereum's active set. When you ask to exit, you do not stop validating immediately and walk away with your stake; you enter a queue, and only a bounded amount of validating weight is allowed to exit per epoch. The same churn limit applies symmetrically to activations. The result is that the active validator set changes only gradually, never in a sudden mass departure.
This deliberate friction is a security feature, not bureaucratic drag. If validators could all exit instantly, a coalition that controlled a supermajority at some checkpoint could finalize that checkpoint, immediately exit and withdraw, and then — with their now-unbonded keys safely beyond the reach of slashing — sign a conflicting alternative history. By forcing exits to drip out slowly, the queue keeps the keys behind any recently finalized checkpoint still bonded and slashable for a meaningful window, which directly bounds the weak subjectivity period and blunts long-range attacks.
Historically the churn limit was expressed as a count of validators per epoch — roughly max(4, active_validators / 65536) entering or exiting, with a separate cap on activations. Since the Pectra upgrade (EIP-7251) introduced large consolidated validators, the limit was re-denominated in terms of balance (ETH/Gwei) churned per epoch rather than a raw validator count, so a few big validators cannot exit faster than many small ones of equal stake. After clearing the queue there is still a fixed withdrawal delay before funds become spendable. In practice, when many stakers exit at once, the queue can stretch to days, and the wait is visible on staking dashboards.
The exit queue is the mechanical reason a finalized Ethereum checkpoint stays defensible for weeks: the stake that finalized it cannot all become slashing-immune overnight, which is exactly what a long-range attacker would need.