Lido’s Curated Module Committee now has authority to alter a 1,500 ETH reserve that gives priority to validator deposits, a setting that can affect how quickly stETH withdrawal requests are finalized when the protocol’s available ETH is under pressure. The committee had not opened a motion to change the reserve as of Sept. 27, according to CryptoSlate.
Why the reserve matters
Lido allows stETH holders to request ETH through a withdrawal queue. To complete those requests, the protocol can draw on ETH held in its buffer. The same buffer can also support deposits into Ethereum validators, creating a potential conflict when withdrawal demand and new staking activity arrive at the same time.
Lido’s contract documentation divides buffered ETH into categories. The deposits reserve is allocated first, followed by an amount reserved for unfinalized stETH withdrawal requests. Any ETH remaining after those allocations is unreserved and can also be used for validator deposits.
The current target for the protected deposits reserve is 1,500 ETH. The effective amount can be lower when the buffer contains less ETH, and the reserve is reduced as deposits are made. An accounting oracle report can restore it toward the target. A lower target takes effect immediately, while an increase waits for the next report before additional ETH receives deposit priority.
The setting becomes most important when the buffer cannot comfortably satisfy both uses. A target of zero would remove the protected slice, allowing ETH that had been earmarked for deposits to be available to the withdrawal reserve instead. That could improve access to buffered ETH for pending withdrawals, but it would not by itself guarantee immediate finalization. The queue, available ETH and validator exit conditions would still matter.
When the buffer has enough ETH for both deposits and withdrawals, the reserve target has little effect on pending requests.
Committee considers a temporary change
The committee received the new authority on Sept. 25 through a 5-of-9 multisignature arrangement. It can initiate Easy Track motions for this specific target, up to 9,600 ETH. The Lido DAO can object to a motion, set the target itself, revoke the authority or remove the factory used for the setting.
The committee said the original 1,500 ETH reserve helped seed Curated Module v2 during the move from Lido’s earlier curated module. It now considers the migration keys to have been seeded, while the existing Community Staking Module has relatively few depositable keys ahead of the planned 0x02 version.
Its proposed sequence is to remove the protected reserve temporarily by setting the target to zero. The committee argues that the existing setting mainly directs stake toward the older curated module, rather than addressing an immediate supply of depositable keys.
The committee could later restore a reserve of between 1,500 and 2,000 ETH after the permissionless 0x02 Community Staking Module launches, if node operators show demand for new validators. Keeping a reserve would help preserve ETH for deposits even during a period of heavy withdrawals. However, changing the target cannot create validator keys that are not available.
The committee has referred to an expected October launch, while Lido’s documentation gives a broader fourth-quarter target. The timing of any renewed deposit priority therefore depends on the module’s launch and the capacity and demand of participating operators. As of Sept. 27, on-chain target-setting events still showed 1,500 ETH, and no reserve-factory motion had been created since the authority was activated.
Model estimates the withdrawal trade-off
The analysis used to assess the initial reserve drew on 360 days of historical staking inflows and withdrawal requests. It ran 500 simulations, each resampling 100 days. Its high-stress scenario assumed about 30 days for Ethereum’s validator exit queue, plus roughly five days for skimming and oracle processing.
The model measured ETH-weighted average time from a stETH withdrawal request to Lido finalization. It is a scenario analysis rather than a forecast, and actual waiting times can differ with live queue conditions.
With a 1,500 ETH reserve, the modeled normal-case average finalization time rose from 2.3 days under a zero-reserve setting to 2.6 days. In the high-stress case, the averages were 7.9 days with the 1,500 ETH reserve, compared with 6.3 days at zero. A 2,000 ETH target produced a modeled stressed average of 8.5 days.
The study also included a 10,000 ETH scenario, although that exceeds the committee factory’s 9,600 ETH limit and no 9,600 ETH row was provided. The comparisons illustrate the modeled cost of preserving guaranteed deposit capacity when buffered ETH is contested; they do not establish the wait for any individual holder.
Market picture
Moneyiar market data recorded Ethereum at $2,681.7028821295 at 22:03 on Sept. 25, 2026, in USD. ETH was down 0.13% over 24 hours and up 2.05% over seven days.
A stETH holder also has an option outside Lido’s withdrawal queue: selling the token on a secondary market. That route depends on available liquidity and the exchange price, while Lido’s withdrawal mechanism has its own finalization process. An Ethereum validator’s network exit is a separate step that can influence how quickly funds become available to complete a withdrawal.
The central issue for Lido is therefore a priority choice. A larger protected reserve preserves more capacity for validator deposits, while a smaller or zero reserve can make more buffered ETH available to withdrawals when both demands compete. The committee’s next action, the launch of 0x02 CSM and the level of operator demand will determine how that balance evolves.
