{"id":13830,"date":"2026-09-28T20:56:40","date_gmt":"2026-09-28T20:56:40","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=13830"},"modified":"2026-09-28T20:56:40","modified_gmt":"2026-09-28T20:56:40","slug":"lido-deposit-reserve-may-reshape-steth-withdrawal-waits","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=13830","title":{"rendered":"Lido deposit reserve may reshape stETH withdrawal waits"},"content":{"rendered":"

<\/p>\n

\n

When stETH holders seek ETH through Lido\u2019s withdrawal queue, the protocol can use ETH in its buffer to finalize their requests. Some of that buffer is also protected for new validator deposits. The more ETH set aside for deposits when both uses compete, the less is immediately available to the withdrawal queue.<\/p>\n

Lido\u2019s Curated Module Committee gained the power to change that priority on Sept. 25. As of Sept. 27, the configured deposit reserve remained at 1,500 ETH, and the committee had yet to open a motion to adjust it. Its first published plan would remove the protected slice temporarily, then consider restoring it for a new staking module. The timing effect for stETH holders depends on how much ETH enters the buffer, how many withdrawals await finalization and whether validators are ready to accept deposits.<\/p>\n

\n

Related Reading<\/span><\/p>\n

Ethereum\u2019s institutional staking boom is growing, but Lido\u2019s share is shrinking<\/h3>\n<\/p>\n

<\/span> <\/div>\n

Where the buffer goes<\/h2>\n

Lido\u2019s contract documentation describes three portions of buffered ETH, allocated in order. A deposits reserve comes first, followed by a reserve for unfinalized stETH requests. ETH left over after both allocations is unreserved and can also fund validator deposits. This order keeps some validator-deposit capacity available when withdrawal demand would otherwise absorb the buffer.<\/p>\n

The 1,500 ETH target governs the protected portion. The effective reserve can be smaller if the buffer holds less ETH; it is spent as deposits are made and restored toward the target with an accounting oracle report. A reduction below the reserve already in place takes effect immediately. An increase waits for the next report before more ETH receives deposit priority.<\/p>\n

The setting matters most when both withdrawal requests and executable validator deposits seek a limited pool of ETH. Setting the target to zero would let the withdrawal reserve claim ETH that had been protected for deposits. Actual finalization still depends on available ETH and the queue, while validator deposits can continue from any unreserved buffer. With enough ETH to cover both uses, the target makes little difference to pending withdrawals.<\/p>\n

The committee said in a Sept. 2 statement that the original 1,500 ETH target helped seed Curated Module v2 during a migration from its earlier curated module. It now says the keys needed for that migration have been seeded and the existing Community Staking Module has few depositable keys before its planned 0x02 version launches. In the committee\u2019s view, today\u2019s protected reserve mainly directs stake toward the older curated module. It proposes setting the target to zero until 0x02 CSM is live.<\/p>\n

The second step would serve different operators. Lido describes 0x02 CSM as a permissionless module approved by the DAO, with a mainnet launch still pending. The committee says it could restore a 1,500 to 2,000 ETH target after launch if node operators provide demand for new validators. That reserve would keep ETH available for deposits into the new module even during withdrawal pressure. The precise setting remains undecided, and a larger target alone cannot create depositable validator keys.<\/p>\n

The committee has pointed to an expected October launch, while Lido\u2019s documentation describes a broader fourth-quarter target. The return of deposit priority therefore depends on a launch and on actual operator capacity. For stETH holders in the protocol queue, the tradeoff would become more acute if withdrawals remained heavy as those new keys became available.<\/p>\n