Lido proposal would delegate deposit-reserve targeting to CMC Easy Track

What happened

A Lido governance proposal would add an Easy Track factory allowing the CMC 5-of-9 multisig to adjust Lido's depositsReserveTarget up to 9,600 ETH.

What changed

The proposal creates a concrete path to delegate recurring control over how buffered ETH is prioritized between new consensus-layer deposits and withdrawal finalization during withdrawal pressure.

What did not change

The proposal is not yet approved or executed. The current role assignment and reserve target are not shown as changed, and the proposed permission cannot transfer funds, mint, burn, or change fees.

Confirmed

• The proposed trusted caller is the CMC 5-of-9 multisig at 0x2570e0b22AD904501dfB0d49575991ACB801dD91.
• The proposed factory is limited to Lido.setDepositsReserveTarget(uint256).
• The proposed immutable maximum target is 9,600 ETH.
• The DAO Agent would retain the ability to set the target directly, revoke the permission, or remove the factory.

Still open

• Completion and findings of the planned security audit.
• Whether the next Aragon vote will grant BUFFER_RESERVE_MANAGER_ROLE and register the factory.
• The final review cadence and reporting format for CMC motions.
• Whether any later execution reaches Ketju's withdrawal-mechanism kill criterion.

What it means for an advisor

• Monitor the audit, Aragon vote, and any executed Easy Track motions because the delegated parameter affects withdrawal-finalization priority under stress.
• Do not mark the Lido withdrawal-mechanism criterion as fired while the change remains only proposed.