Lido’s liquidity and the Ethereum exit queue
Ethereum staking queues shifted as a 850,000 ETH validator exit surge, largely driven by MetaMask infrastructure issues, was met by fresh inflows. Lido manages treasury stability through the NEST program and automated LDO buybacks to mitigate market volatility.
Ethereum’s staking queues shifted recently as fresh inflows overtook exits. This shift marks a reversal from the massive exit wave in late 2025. During that period, the validator exit queue reached 850,000 ETH. This surge stemmed from MetaMask Staking infrastructure issues tied to Lido operations. The event pushed the unstaking queue up 392%. The entry queue contains 745,619 ETH with a 13-day wait, while the exit line sits at 360,518 ETH with an eight-day delay. In mid-September, the exit queue reached 2.5 million ETH, which is 2% of the total staked supply. The exit volume in late September was 100,000 ETH, but the queue jumped to 850,000 ETH by October 2. Of this 850,000 ETH, 523,000 ETH came from MetaMask’s validators. This exit was a precautionary measure after MetaMask disclosed a compromise in its infrastructure on September 30. In a two-week window, the 27 distinct LSD platforms saw a decline of 60,000 ETH. Lido accounted for 40,000 of those withdrawn ETH. Since April 1, the total LSD ecosystem exodus reached 440,000 ETH, which is \$1.45 billion. The network holds 43.6 million ETH staked across 878,000 active validators.
LDO buyback and the NEST program
Lido DAO manages its treasury through the NEST program and automated LDO buybacks. The protocol executes these trades in 1,000 stETH batches. The Growth Committee limits each trade to a 2% price deviation to avoid slippage. This anti-cyclical mechanism only activates when Ethereum trades above \$3,000 and annual DAO revenue exceeds \$40 million. These rules cap total annual buybacks at \$10 million. Lido also maintains a liquidity pool that pairs LDO with wstETH. Although LDO recently traded at \$0.3201, a level 63% below its two-year average against ETH, the DAO uses these treasury funds to realign valuation with protocol performance. The LDO-to-ETH ratio fell 50% recently. Staking rewards compressed toward 3% as total staked ETH grew faster than issuance and fee income. Fee capture rose from 5% to 6.11% year-on-year. The committee manages purchases across Binance, OKX, and Uniswap with limit orders and dollar-cost averaging. You should watch how these treasury outflows influence LDO price stability when market volatility persists.
| Feature | Parameter / Limit |
|---|---|
| NEST Buyback Cap | \$10 million annually |
| NEST Market Impact | 2% maximum per trade |
| NEST ETH Price Floor | \$3,000 |
| NEST Revenue Floor | \$40 million |
| NEST Batch Size | 1,000 stETH |
Whale movement and withdrawal mechanics
Sophisticated capital movement defines the current DeFi environment. Over a one-year period, 105 whale addresses withdrew more than \$10 million each from Lido. These withdrawals totaled approximately \$3.45 billion in ETH. These whales accounted for 40% of all withdrawals. They used protocols like Aave v3 and Spark Protocol to redeploy their capital. Spark Protocol saw a retention rate of only 0.48%. Aave v3 saw a retention rate of 19.74%. OneInch saw a retention rate of 56.23%. Lido’s market share is 71.41% of the 13.09 million ETH held by LSD platforms. The stETH:ETH pool on Curve holds over \$1.5 billion in liquidity. This liquidity is a support for the token during market stress. The withdrawal process is a method where the holder manages an unstETH NFT that holds the claim to the native ETH once the AccountingOracle finalizes the request within the protocol’s first-in, first-out queue. When users request withdrawals, the protocol mints an unstETH NFT that replaces the staked token. The request locks the stETH. Reward accrual stops until the owner claims the native ETH. Most withdrawals involved principal. Specifically, 86.6% of withdrawals from the 105 whales involved principal rather than rewards. Will the concentration of whale withdrawals eventually deplete the protocol’s withdrawal buffer?
Join the discussion