Lido's deposit reserve sat at 1,500 ETH on Sept. 27, according to on-chain target-setting events at the stETH contract, two days after the protocol's Curated Module Committee received authority to change the setting through a newly activated Easy Track factory.

The committee said in its Sept. 2 reporting thread that the original 1,500 ETH target helped seed Curated Module v2 during a migration from the earlier curated module. With the keys now seeded, the committee wrote, "today's protected reserve mainly directs stake toward the older curated module." It proposes setting the target to zero until Lido's planned 0x02 Community Staking Module (CSM) launches on mainnet, then restoring a 1,500 to 2,000 ETH target after launch if node operators demand new validators.

How does Lido split its withdrawal buffer?

Lido's contract documentation describes three portions of buffered ETH, allocated in order: a deposits reserve, a reserve for unfinalized stETH requests, and unreserved ETH that can also fund validator deposits. The 1,500 ETH figure governs only the protected slice. The effective reserve can be smaller if the buffer holds less ETH; reductions take effect immediately, while increases wait for the next oracle report.

The setting bites hardest when withdrawals and executable validator deposits chase the same pool. Setting the target to zero would let the withdrawal reserve claim ETH protected for deposits. Validator deposits can still pull from any unreserved buffer. When the buffer comfortably covers both uses, the target makes little difference to pending withdrawals, according to the documentation.

What does the stress model show?

An analysis used to size the initial reserve simulated how the choice affects withdrawals. It drew on 360 days of historical staking inflows and withdrawal requests, then ran 500 simulations that each resampled 100 days. Its high-stress case assumes roughly a 30-day Ethereum validator exit queue plus about five days for skimming and oracle processing. Output measures the ETH-weighted average time from a stETH request to Lido finalization.

Modeled outcomes:

• 0 ETH reserve: 2.3 days normal case, 6.3 days high stress
• 1,500 ETH reserve: 2.6 days normal case, 7.9 days high stress
• 2,000 ETH reserve: 2.7 days normal case, 8.5 days high stress
• 10,000 ETH reserve (a scenario above the committee factory's 9,600 ETH cap): 3.6 days normal case, 15.7 days high stress

In the model, protecting 1,500 ETH for deposits raises the normal-case average finalization from 2.3 to 2.6 days against a zero target. Under high stress, the averages stretch from 6.3 to 7.9 days. A larger reserve on its own cannot create depositable validator keys, the analysis notes.

What governance power changed on Sept. 25?

A governance proposal gave the committee's 5-of-9 multisig authority to initiate Easy Track motions for this single target, capped at 9,600 ETH. The DAO can object to a motion, set the target directly, revoke the permission or remove the factory. The ceiling limits the committee's setting through this route, though a single motion can still span the permitted range.

On-chain logs at the reserve factory showed no creation events since its Sept. 25 activation, and the configured target on the underlying contract stayed at 1,500 ETH through Sept. 27.

What is the next signal to watch?

The committee has pointed to an expected October mainnet launch for 0x02 CSM, while Lido's own documentation describes a broader fourth-quarter target. The return of deposit priority therefore hinges on a launch and on actual operator demand for new validators. For stETH holders in the queue, the tradeoff would sharpen if withdrawals stayed heavy as those new keys came online, since both would compete for the same buffered ETH.

A written motion from the committee to move the 1,500 ETH number, or its absence as the launch window opens, will set the direction.