Why Does Ethereum Native Staking Require a 32-Day Queue?

If you recently participated directly in Ethereum native staking, you may have noticed that although your ETH was deposited and the on-chain transaction succeeded, your validator remains stuck in "queueing" and has not yet started working.

And this row is likely to last over a month.

As of September 16, over 1.8 million ETH remain pending entry into the validator set, with an estimated waiting time of approximately 32 days; in July of this year, the waiting time peaked at over 43 days, and at the height of the queue in March, around 3.4 million ETH were waiting at the entrance, with waiting times nearing 60 days.

In other words, "waiting in line for a month" is not an exaggeration.

But problems随之而来。

Ethereum produces a new slot every 12 seconds on average, so regular transactions are confirmed quickly—so why does staking require billions of dollars worth of ETH to wait weeks on end? More importantly, are there any earnings during those weeks? Why does entering staking now take over a month, yet exiting can take just minutes?

The answer lies in a crucial but often overlooked mechanism of Ethereum: the Validator Queue.

Let’s start with the most common misconception: Ethereum does not require newly staked ETH to be locked for 40 days before it can begin working.

One month is just a dynamic result.

In simple terms, you can think of it as: the ETH waiting in line divided by the amount of ETH allowed per day on Ethereum = approximate wait time.

Ethereum's PoS does not allow all new validators to enter the network at once; instead, it implements a churn limit mechanism that controls the maximum amount of staked balance that can join the validator set per epoch.

An epoch consists of 32 slots, with each slot lasting approximately 12 seconds, making an epoch about 6.4 minutes long, and roughly 225 epochs occur each day.

After Pectra/Electra, Ethereum began calculating this cap based more on "ETH balance" rather than simply the number of validators. Currently, the processing limit for new staking is 256 ETH per epoch, which, if converted entirely into traditional 32 ETH validators, equates to a maximum of 8 standard validators being approved every 6.4 minutes.

It’s easy to calculate how much ETH can be entered in a day: 256 ETH × 225 ≈ 57,600 ETH/day.

So if there are approximately 1.83 million ETH waiting to enter, that’s 1.83 million ÷ 57,600 ≈ 32 days, which is the core source of the “one-month wait” phrase.

Therefore, this number changes daily.

If fewer than 57,600 ETH enter the queue each day, the backlog will gradually decrease, reducing the wait time from 40 days to 30 days or even 20 days. Conversely, if more than this amount of ETH enters daily, the queue will not shorten—it will grow longer.

In March this year, approximately 3.4 million ETH queued up, waiting for nearly 60 days, serving as an extreme example.

So it’s actually two different things from what we commonly mean by “whether Ethereum is congested.”

Low gas fees and ample block space do not mean validators can join immediately, because the limiting factor is not the execution layer’s transaction capacity, but rather an intentional validator entry rate limiter set by Ethereum.

Since waiting for dozens of days means funds cannot generate staking rewards, the most straightforward solution seems simple: just raise the limit of 256 ETH per epoch.

The issue is that validators are not ordinary accounts.

After an ETH transfer is completed, it imposes almost no ongoing burden on the network; however, once a validator is activated, it becomes a long-term participant in Ethereum’s consensus system, engaging in block attestations, committee assignments, and network consensus.

Ethereum currently has over 900,000 active validators, with more than 42 million ETH staked. Each new validator becomes part of this massive consensus system.

This is also why Ethereum has been actively controlling the rate of change in the validator set.

EIP-7514, proposed in 2023, specifically set a cap on the rate at which validators can be activated. The concern behind it is not that "too many people staking is bad"—on the contrary, it is that unchecked rapid growth in the number of validators would lead to increased state size on the consensus layer, greater validator management overhead, and heightened pressure on network communication and processing.

After the Pectra upgrade, Ethereum allows the effective balance of a single staking validator to be increased up to 2048 ETH, partly to reduce the need to split large amounts of staked ETH into thousands of 32 ETH validators, thereby alleviating the additional burden caused by the continuous growth in the number of validators.

But beyond that, the Churn Limit also has a more fundamental purpose: to prevent drastic changes in the group of people maintaining Ethereum's security over short periods of time.

After all, the security of a PoS network depends on the current set of active validators.

If large amounts of staked funds could instantly enter or exit, the network’s basis for determining who is eligible to participate in consensus and how much economic security remains in the system would change rapidly; therefore, Ethereum imposes a human-defined upper limit on the speed of such changes.

This is also why "queuing" is not a bug to be fixed.

From the user’s perspective, it does sacrifice some capital efficiency; but from the protocol’s standpoint, this is more like a deliberate speed bump, signaling that Ethereum would rather have millions of ETH waiting at the door for weeks than allow the set of validators to suddenly expand or contract over just a few days.

Even looking ahead to the future roadmap, this approach remains unchanged.

The currently planned inclusion of EIP-8061 in Glamsterdam aims to significantly enhance the capacity for processing exits and validator merges to alleviate exit congestion, while still maintaining the 256 ETH/epoch cap on the activation side.

In other words, Ethereum is considering making it more flexible to go out, but is not yet ready to fully open the gates for coming in.

So, if ETH has been deposited, does the waiting month count as staking?

From the perspective of protocol rewards, it does not count.

Only after a validator truly enters the Active, or "active," state will it begin performing attestations, participating in block proposals, and earning corresponding Ethereum protocol rewards.

Before this, even if the staking transaction was completed and ETH had entered the staking process, no normal validator staking rewards were generated as long as the validator remained in Pending status. Ethereum.org considers "Active" as the point at which validators begin working and generating rewards.

This is also where the long queue truly affects ordinary users.

Based on the current network-wide staking APR of approximately 2.6%, a 32 ETH validator waiting 40 days would forgo roughly 0.09 ETH in potential protocol rewards.

Individually, this may not seem excessive, but for an institution that needs to deploy tens of thousands or even hundreds of thousands of ETH, the cost of idle capital over 40 days can quickly escalate.

This also explains why the Ethereum staking queue has recently attracted increasing attention from institutions and ETH treasury firms. In the past, people primarily compared different staking options by looking at minor differences in APR or fee structures; but now that waiting in the queue itself can last over a month, “when actual yield generation begins” has become part of capital efficiency.

However, there is another interesting contrast here.

If you check the exit queue, you'll find that wait times are often just a few minutes to a few hours—so does Ethereum allow everyone to exit quickly but not enter quickly?

Actually, no. Both entry and exit have churn limits, and both are subject to protocol rate limits; however, the final queue length depends on how many people are waiting.

Over 2 million ETH are currently waiting to enter, while very few ETH are waiting to exit—making it like a highway where one side has a queue stretching dozens of kilometers, while the other side remains nearly clear.

Moreover, "a short exit queue" does not mean ETH will immediately return to your wallet within minutes. After the validator completes its exit, it must still wait for a fixed period of 256 epochs—approximately 27 hours—before entering the withdrawable state. After that, the funds must still wait for Ethereum’s automatic Withdrawal Sweep to transfer them to your withdrawal address, which may add several more days to the process.

For regular users, this also means there’s a subtle but easily overlooked difference between various staking methods.

If you choose to run your own validator or create an independent validator through a non-custodial ETH staking service like imToken, the underlying process still requires your validator to officially join the Ethereum validator set, and thus must go through this protocol queue. For example, in imToken’s non-custodial staking, users hold the withdrawal key while the node service provider operates the validator; when the interface shows “Queuing,” it means the validator is waiting for Ethereum to approve it, and only after its status changes to “Active” does it begin generating protocol rewards.

Some liquid staking pools, due to the presence of a large number of active validators and liquid tokens, can abstract this waiting period at the product level, so users may not directly experience the "zero-reward waiting period" of several dozen days.

However, the cost is the introduction of another set of trust boundaries, including additional risks such as smart contracts, LST liquidity, protocol governance, and asset swapping—a problem often obscured by APR, since the true cost of staking is never just about fees and yields.

When funds enter, when they truly begin to work, when you can withdraw, and who controls the assets during this process are all inherent parts of the staking product.

On the surface, Ethereum allowing millions of ETH to wait at the door for over a month seems like a rather inefficient design.

But if you shift your perspective to the entire network, it becomes clear: ordinary transactions aim for quick execution, while validators are responsible for maintaining the next moment of Ethereum's consensus.

The former can strive for ever-increasing speed, while the latter requires restraint.

So, this is essentially a previously invisible safety barrier that has turned into a visible long queue due to staking demand far exceeding the protocol’s set entry rate.

In a sense, the longer this queue grows, the more it indicates that, at this stage, the demand to stake and join the Ethereum validator set continues to outpace the rate at which the protocol allows new entries.

But no matter how many people are waiting outside, Ethereum will only open its doors at its own pace—one epoch at a time.