Lido DAO has carried out Aragon Vote #205, a governance package that updates several parts of its operating framework at once. The vote closed and was executed on September 21 at 13:45 UTC, moving the approved changes onchain rather than leaving them as a pending proposal.

The bundle includes the LIP-37 Execution Delegation Framework, an upgrade of the DepositSecurityModule to version 5, operational key rotations for Kiln and Stakely, and a new mechanism for managing deposit reserves. Together, the measures revise how Lido handles delegated authority, permissions, and ETH set aside for deposits.

A bundled governance package

Vote #205 was not limited to a single technical adjustment. Instead, Lido DAO approved a broader package touching execution delegation, security tooling, operator administration, and reserve management in one action.

According to the proposal outcome, the changes have already been executed onchain. That means the package now forms part of Lido’s active operating setup, rather than representing a future governance plan.

What the vote changed

One of the central items in the package is adoption of the LIP-37 Execution Delegation Framework. The vote also upgrades Lido’s DepositSecurityModule to v5, a change that sits alongside the governance overhaul rather than apart from it.

In addition, the DAO rotated operational keys for Kiln and Stakely. It also created a Deposit Reserve Target Easy Track factory, adding a new governance tool around how deposit reserves can be managed within the protocol’s structure.

New reserve controls

The newly approved reserve mechanism introduces a ceiling of 9,600 ETH. The source article says this cap will sit under CMC oversight, making the reserve limit part of a defined supervisory arrangement rather than an open-ended setting.

In practical terms, the reserve-related changes affect how much ETH can be held back for deposit purposes and how that reserve is governed. Alongside the delegation and permissions updates, this establishes a more explicit operating baseline for handling reserved funds.

A more formal operating model

The broader significance of Vote #205, as described in the source article, is less about a single feature and more about the direction of Lido’s governance. As the protocol has become a major part of Ethereum’s staking infrastructure, its proposals increasingly look like formal control and risk-management updates.

This package fits that pattern by defining how authority is delegated and how safeguards are applied around the movement and management of large amounts of staked ETH. With the vote already executed, node operators, delegates, and users now have a confirmed new framework for these areas of protocol operation.

What happens next

The next confirmed step is implementation under the newly approved framework, since the vote has already been executed onchain. From here, the relevant LIP-37 delegation rules, DepositSecurityModule v5 changes, operator key rotations, and reserve controls become the active reference point for Lido’s ongoing operations.

The result is a clearer set of governance-backed rules around execution delegation, operational permissions, and deposit reserve management, with the 9,600 ETH reserve ceiling serving as one of the package’s concrete new limits.

Source: bitcoinist.com