
“Liquid” and “instant” are not the same word. When you stake ETH, the protocol, not the service you use, decides how fast stake can leave. That limit is arithmetic in the consensus specification, and it was rewritten in the Pectra upgrade of May 2025.
The clock
Ethereum’s proof-of-stake documentation divides time into slots of 12 seconds and epochs of 32 slots. An epoch lasts 384 seconds, so a day holds 86,400 divided by 384, which is 225 epochs. Every rate limit below is counted per epoch.
The limit since Pectra
Before Pectra, churn was counted in validators. EIP-7251, part of Pectra, raised the maximum effective balance of a validator from 32 to 2048 ETH while keeping 32 ETH as the activation minimum, so counting validators no longer made sense. The Electra consensus specification now counts churn in ETH. Its function for activations and exits returns the smaller of two values: MAX_PER_EPOCH_ACTIVATION_EXIT_CHURN_LIMIT, set to 256 ETH, and a balance-based limit equal to total active stake divided by a quotient, with a floor of 128 ETH.
In plain numbers: at most 256 ETH can exit per epoch. Over 225 epochs that is at most 57,600 ETH per day, the same ceiling for entries. When more ETH than that wants to leave, it waits its turn.
What that means for a single staker
Your wait is roughly the ETH ahead of you in the queue divided by 57,600 per day, plus the time for your validator to be swept for withdrawal afterwards. Ethereum.org’s withdrawals page describes that sweep: at most 16 withdrawals per block, about 115,200 per day assuming no missed slots, so a full pass over 800,000 validators takes about seven days. Exiting “takes variable amounts of time, depending on how many others are exiting at the same time”.
The queue is longest when the most people want out. That is the purpose of the limit: it protects the network’s security from a sudden mass exit, and it means no staking provider can promise a fixed exit time during stress.
Pectra also changed how exits are triggered
EIP-7002, also in Pectra, introduced a contract through which an exit can be triggered with the execution-layer withdrawal credentials, without the validator’s signing key, according to ethereum.org. For delegated staking that matters: the holder of the withdrawal address can start an exit even if the operator does not cooperate. Validators with compounding (0x02) credentials can hold balances above 32 ETH; below the 2048 ETH ceiling their balance compounds, and a partial withdrawal is requested from the execution layer rather than swept automatically.
Liquid staking does not escape the queue
A liquid staking protocol’s redemptions ultimately pass through the same exit limit. A holder who wants out faster sells the token on the market, which is why a long exit queue tends to show up as a market discount. See a liquid staking token is a claim, not ETH.
A worked example
Suppose 1,152,000 ETH is waiting to exit when you submit your request. At the ceiling of 57,600 ETH per day, the queue ahead of you clears in 1,152,000 ÷ 57,600 = 20 days. If the queue holds 115,200 ETH instead, the wait is two days. The arithmetic is the same in both cases; only the number of people leaving at the same time differs. These figures are illustrations, not readings: the live queue length changes constantly, and beacon-chain explorers publish it. Check the explorer on the day you plan to exit, not on the day you staked.
Your own validator’s size matters too. Since churn is counted in ETH, a consolidated validator with a large balance uses up more of an epoch’s limit than a 32 ETH one, so its exit can be scheduled across several epochs. And the exit epoch is not the end of the wait: the consensus specification adds a minimum delay of 256 epochs, about 27 hours, before an exited validator’s balance becomes withdrawable, and only then does the sweep have to reach it.
Entry works the same way
Since Pectra, deposits pass through a similar ETH-denominated limit on the way in, so a rush to stake also queues. A long entry queue means new stake waits before it earns rewards; a long exit queue means existing stake waits before it can be withdrawn. Both are visible on public explorers, and both are worth checking before choosing between running a validator, delegating to an operator or buying a liquid staking token. None of those choices removes the queue; they decide who waits in it and who carries any price difference while it lasts.
If you rely on a staking provider, ask whether the withdrawal times it states are estimates based on the current queue or promises. The protocol does not let anyone guarantee them during a rush.
The Settlement Test
- What settles: the exit itself, at the epoch the queue reaches you; then the withdrawal, when the sweep reaches your validator and credits ETH to the withdrawal address on the execution layer.
- What it costs: the time in queue, rewards forgone after exit, and gas for any execution-layer request.
- What breaks: nothing, in the protocol sense; the limit works as designed. The failure is a plan that assumed an exit would be quick during a rush.
For the full picture of what a quoted yield omits, read what a staking yield leaves out; for definitions, see withdrawal credentials and slashing. The staking yield estimator works from a rate you supply.
Primary sources
Educational content, human-edited and possibly AI-assisted. It describes how systems work and is not financial, legal or tax advice. Report an error via our corrections page.


