Lido’s 1,500 ETH deposit reserve could lengthen the time stETH holders wait for withdrawals when the protocol’s available buffer is under pressure.
Lido uses ETH held in its buffer to complete withdrawal requests, while also keeping part of that balance available for deposits into new validators. The more ETH protected for deposits, the less is immediately available to process withdrawals.
The Curated Module Committee received authority to change that priority on 25 September. The configured reserve was still 1,500 ETH on 27 September, and no motion to alter it had been opened. Its initial plan is to remove the protected allocation temporarily before considering whether to restore it for a new staking module.
The impact on stETH withdrawals depends on the amount of ETH in the buffer, the number of outstanding requests and whether validators are ready to accept further deposits.
How the reserve works
Lido’s contract documentation allocates buffered ETH in three stages. The deposits reserve is applied first, followed by ETH for unfinalised stETH withdrawal requests. Any remaining balance is unreserved and can also be used for validator deposits.
The 1,500 ETH figure is a target rather than a guaranteed balance. The effective reserve can be lower when the buffer contains less ETH, and it is reduced as deposits are made before being replenished towards the target through an accounting oracle report. A lower setting applies immediately, while an increase takes effect only after the next report.
The reserve matters when withdrawal requests and ready validator deposits are competing for the same limited ETH. Setting the target to zero would allow the withdrawal allocation to use ETH previously protected for deposits. Withdrawals would still depend on the queue and available funds, while deposits could continue from any unreserved ETH.
The committee said on 2 September that the original 1,500 ETH target helped support Curated Module v2 during its migration from the previous curated module. It now believes the relevant migration keys have been seeded, while the existing Community Staking Module has only a small number of depositable keys before the planned launch of its 0x02 version.
It has proposed reducing the target to zero until 0x02 CSM goes live. Lido describes 0x02 CSM as a permissionless, DAO-approved module, although its mainnet launch remains pending. The committee could later restore a reserve of between 1,500 and 2,000 ETH if node operators demand capacity for new validators.
The committee has indicated an October launch, whereas Lido’s documentation gives a broader fourth-quarter timeframe. The return of deposit priority therefore depends both on the launch and on operators being able to provide validator capacity.
Modelled effect on withdrawals
The analysis used to set the reserve examined 360 days of historical staking inflows and withdrawal requests. It ran 500 simulations, each resampling 100 days, and modelled a high-stress situation involving about 30 days in Ethereum’s validator exit queue plus roughly five days for skimming and oracle processing.
Under the model, average finalisation times were:
– 0 ETH reserve: 2.3 days normally; 6.3 days under high stress
– 1,500 ETH: 2.6 days normally; 7.9 days under high stress
– 2,000 ETH: 2.7 days normally; 8.5 days under high stress
– 10,000 ETH scenario: 3.6 days normally; 15.7 days under high stress
The 10,000 ETH case exceeds the committee factory’s 9,600 ETH limit, and no 9,600 ETH scenario was included.
The governance proposal gives the committee’s 5-of-9 multisig power to initiate Easy Track motions for the reserve, up to 9,600 ETH. The DAO can block a motion, set the target itself, withdraw the permission or remove the factory.
On-chain events still showed a 1,500 ETH target on 27 September, with no new reserve-factory motion recorded since the authority was activated on 25 September. The effect on withdrawals will depend on whether heavy stETH demand coincides with ETH being needed for deposits.
