Lido’s 1,500 ETH reserve could slow stETH withdrawals

A 1,500 ETH deposit reserve in Lido’s buffer reduces ETH available to finalize stETH withdrawals and can lengthen finalization times when withdrawal demand rises.

Lido holds a buffer of ETH that the protocol uses both to finalize stETH withdrawal requests and to fund new validator deposits. A configured deposit reserve of 1,500 ETH is kept separate from the portion allocated to unfinalized stETH requests and any remaining unreserved ETH. When both uses compete for the same pool, funds set aside for deposits are not available to finalize withdrawals.

The reserve target is applied in order: the deposits reserve is preserved first, then a reserve for pending stETH finalizations, and any leftover is unreserved. If the buffer contains less than the target, the effective reserve shrinks automatically and reductions below the target take effect immediately. Increases to the target become active only after the next accounting oracle report.

Lido’s Curated Module Committee received power on Sept. 25 to change the deposit-reserve target via Easy Track motions, with a ceiling of 9,600 ETH. On-chain settings showed the target remained 1,500 ETH as of Sept. 27 and no motion had been opened. The committee published a plan to set the target temporarily to zero, freeing previously protected ETH for withdrawal finalization, and later consider restoring a 1,500–2,000 ETH target for a new staking module, 0x02 CSM, once operator keys and demand are in place. The committee wrote that the original 1,500 ETH target “helped seed Curated Module v2.” Committee materials point to an expected October mainnet window for 0x02 CSM, while broader protocol documentation cites a fourth-quarter timeframe.

Lido conducted a stress test using 360 days of historical staking inflows and withdrawal requests and ran 500 simulations that resampled 100-day slices. In the model’s normal case, a 0 ETH deposit target produced an average finalization time of about 2.3 days and a 1,500 ETH target produced about 2.6 days. In a high-stress scenario-assuming about a 30-day Ethereum validator exit queue plus roughly five days for skimming and oracle processing-the model showed averages of 6.3 days with a 0 ETH target and 7.9 days with a 1,500 ETH target. A 2,000 ETH target raised the modeled high-stress average to 8.5 days. A hypothetical 10,000 ETH scenario produced longer averages but exceeds the committee’s 9,600 ETH limit.

Setting the target to zero would allow withdrawals to use ETH that had been earmarked for deposits, while validator deposits could still draw from any unreserved portion of the buffer. The timing for any restored deposit priority depends on the availability of operator keys and a mainnet launch date for 0x02 CSM. Individual stETH holders’ finalization times will depend on the buffer size, the number of pending finalizations and whether validators are ready to accept deposits.

Governance mechanics constrain changes. The committee’s 5-of-9 multisig can initiate Easy Track motions for this single parameter up to the 9,600 ETH ceiling. The DAO retains options to object, set the target directly, revoke the committee’s permission or remove the reserve factory. On-chain records showed no factory motion between the committee’s Sept. 25 activation and Sept. 27.

Articles by this author