Skip to content
Blockchain Posts

on-chain

Ethereum exit queue hits 850K ETH as MetaMask drives 61% of 2026 high

Beaconcha.in puts the ETH exit queue at 850,736 ETH on Oct 2, a ~14.77-day wait. MetaMask Staking's precautionary exits account for ~523,000 ETH across 17,000 validators.

by 3 min read
on-chainethereummetamasklidoinfrastructure

Ethereum's validator exit queue reached 850,736 ETH on October 2, 2026, its highest level this year, according to beaconcha.in's validator queue page tracked by Crypto Briefing and Tokenpost. Estimated withdrawal wait sits at ~14.77 days. The queue was in the low-to-mid 100,000 ETH range in late September — a ~392% jump since October started.

What's driving it

MetaMask Staking is the dominant driver. The out-of-order precautionary exit disclosed on September 30 after an infrastructure incident put ~17,000 validators representing ~523,000 ETH into the queue — about 61% of the total. Lido's research-forum post set an end-of-October-7 completion target for those exits.

The remaining ~40% looks like opportunistic profit-taking at current prices rather than a second incident. Mining-pool veteran Jiang Zhuoer was cited in on-chain commentary suggesting participants are locking in gains while queue capacity is available. There is no second named validator operator currently exiting in volume.

Why it matters

Ethereum's exit queue is rate-limited by the protocol: at a target active validator count north of 878,000, the maximum churn per epoch (6.4 minutes) caps how fast ETH can leave the active set. When the queue builds, every subsequent exit — opportunistic or forced — gets pushed back further. The 14-day round-trip for exiting ETH, plus the entry queue on re-staking, means ETH that leaves the beacon chain today is roughly a 45-day round trip before it can re-stake.

Impact spreads across:

  • LSD operators. Lido holds ~22.08% of staked ETH; MetaMask Staking (the former Consensys Staking operator set) is one of its node operators, not the share itself. Rocket Pool, Ether.fi, Kiln and Figment have not reported out-of-order exits of a comparable scale.
  • Restaking. EigenLayer AVSes relying on fresh ETH deposits see slower validator entry while the entry queue sits behind this exit wave.
  • Market plumbing. Despite the queue size, spot ETH stayed inside a ~$2,686–$2,725 band through the surge — the pending supply is spread across the wait rather than hitting markets at once.

Numbers

- Exit queue (Oct 2)         : 850,736 ETH
- Est. exit wait              : ~14.77 days
- Active validators (approx.) : ~878,089
- Total staked ETH (approx.)  : ~43.6M (queue = ~2% of staked)
- MetaMask Staking share      : ~17,000 validators, ~523,000 ETH (~61% of queue)
- Lido operator share         : ~22.08% of all staked ETH
- Round-trip exit→re-stake    : ~45 days at current entry+exit queue depth
- Source                      : beaconcha.in validator queue

What to watch

  1. MetaMask final exit date (Oct 7). Lido's forum timeline has all MetaMask validators out by end-of-day October 7. Any slippage past that date is a signal the exits are not purely precautionary.
  2. MetaMask incident disclosure. No vector, affected systems, or data-impact assessment has been published yet. Our prior write-up on MetaMask Staking and the Morpho side effect tracks the open questions.
  3. Entry queue reversal. If, by mid-October, MetaMask's exited ETH re-enters via Lido or re-deploys to a new operator set, the entry queue will balloon with the same 523K ETH on a lag. Watch for a mirror spike.
  4. Operator concentration post-event. Lido's node operator roster publishes composition data; if MetaMask doesn't re-apply, the slot gets redistributed and operator-concentration metrics shift.

Context

Previous queue peaks in 2024 and 2025 came from Celsius-era claim distributions and Shapella-adjacent withdrawals, not from a single named operator. This is the largest single-operator precautionary exit event since Lido's node operator model began, by both validator count and ETH size. The precedent to watch is whether other LSD designs tighten key-management or operator-slashing policies around infrastructure incidents that don't touch withdrawal keys.

Related stories