stVaults Committee Proposal

Background

Lido contributors are preparing to launch the V3 Protocol upgrade, which is currently in testing and planned for release later this fall. You can read more about V3 and stVaults in the announcement post or the white paper.

Committee purpose

The Lido V3 stVaults risk assessment framework allows for flexibility in fees and the reserve ratio for specific vaults depending on specific circumstances, such as: the Node Operator(s) involved, or particular business cases. To handle requests from Vault Owners and Node Operators for non-default terms, as well as to monitor stVaults’ performance, it is proposed to create an stVaults Committee.

Responsibilities

Committee members should pursue two primary objectives, in this order:

  1. Ensure protocol security and resilience

  2. Enable stake growth and DAO fee efficiency

It is proposed that the committee multisig, acting on-chain on behalf of the committee, where committee decisions should be made by consensus, will be granted the ability to configure stVaults and/or Node Operator Tiers, within the confines of the Easy Track optimistic governance process:

  • Set the reserve ratio for specific tiers or vaults.

  • Define the default and custom tier grids for node operators.

  • Set DAO fee values for specific vaults and for tiers within a given node operator’s grid.

  • Bad debt compensation management between vaults/tiers in complex cases like mass slashing.

The committee should primarily rely on the stVault risk framework when assessing situations and making decisions. All on-chain actions will go through Easy Track, the Lido DAO optimistic governance process which enables LDO-holders to object to Easy Track motions over a 72 hour period.

Funding

No additional funding is required other than transaction gas for committee on-chain actions, which will be requested from the Gas Supply Committee.

Committee composition

It’s proposed to include the following members on the committee with a signing threshold of 3/5:

  • @Mol_Eliza, co-author of the assessment framework and Lead Analyst at Lido Labs.

  • @mikgur, co-author of the risk assessment framework and Analytics Team Lead at Lido Labs.

  • @Marin, Head of Protocol Relations at Lido Ecosystem.

  • @KimonSh, Head of Node Operator Mechanisms at Lido Labs.

  • @dmitrii_v, Lead Product Manager and contributor on the stVaults team at Lido Labs.

Committee members must avoid conflicts of interest; if any potential overlaps arise, they must disclose the associated conflict(s) and the committee must decide on how to proceed with the affected cases/assessments (e.g. recusal of affected member(s) from the relevant decision).

The committee’s lifespan

The committee will remain in place until its responsibilities are fully automated or stVaults are decommissioned.

Tokenholders may object to the committee’s in-flight motions made via Easy Track; alternatively, full on-chain votes can also be made that override committee-set values, or to set new values directly. Ultimately, if the DAO disagrees with the committee’s overall performance, it has the power to dissolve the committee, instruct the committee to replace participating members via a governance vote, or entirely substitute the committee for another committee or mechanism.

Reporting

All committee actions will be tracked via Easy Track. In addition, the Committee will create a dedicated analytics dashboard to monitor stVaults performance — specifically fee efficiency and stVaults’ impact on the overall protocol.

Next Steps

After the forum discussion, if the community raises no major objections, it is suggested that the proposal will be included in one of the upcoming snapshot voting slots. Stay tuned.

12 Likes

How will the committee ensure transparency in decision-making beyond the Easy Track process? Will detailed rationales for each adjustment be published?

2 Likes

Hi Sophia, the intent is to provide a transparent rationale for the Easy Track changes; most likely, it will be posted on the forum.

2 Likes

Snapshot vote started

The Establish the stVaults Committee Snapshot has started! Please cast your votes before Mon, 29 Sep 2025 16:00:00 GMT :folded_hands:

I understand the concerns about introducing a new system and the need for initial oversight.

But I’m concerned that we haven’t set any time limits for this committee in advance.
It would be more effective to give it a specific timeframe to bring the system to an optimal state and understand the need for manual control.

While I consider this proposal useful, it would be good to add specific time limits for this committee’s authority during the on-chain voting phase. If such a committee proves necessary, then elections should be held.

Snapshot vote ended

The Establish the stVaults Committee Snapshot vote concluded!

The results are:
:white_check_mark: Support: 57.9M LDO
:cross_mark: Reject: 102 LDO

2 Likes

Hi everyone!

As a stVaults Committee member, I inform the community about the upcoming rotation of stVault Committee members.

  1. @Marin will be replaced by @Willem, in response to internal changes in responsibilities. @Willem is a Protocol Relations team member at Lido Ecosystem.

  2. Two new members will join the Committee to strengthen it from the technical and operations sides:

    1. @Kate_Alekseeva - DAO Ops manager at Lido Labs.
    2. @AlexDry - Protocol Developer and contributor on the stVaults team at Lido Labs.

Due to the increasing number of Committee members, the signing threshold will also be changed from 3/5 to 4/7.

3 Likes

Hi!

I would like to announce my intention to become a signer of the stVaults committee multisig with address 0xdf87a36f6c753e85f06e3a7a595dbd3f9bcd4937.

Here’s the verification: Ethereum Verified Signed Message

3 Likes

Hi!

I’d like to inform the community about my intention to become a signer of the stVaults Committee multisig with address 0x512B58efaef534Af685F7638c177B927650eF995.

Verification: Ethereum Verified Signed Message

3 Likes

Hi!

I’d like to inform the community about my intention to become a signer of the stVaults Committee multisig with address 0x28939ef21690Fe8358E93d661d1ce6d7fA9154F3.

Verification: Ethereum Verified Signed Message

2 Likes

Hi!

I’d like to inform the community about my intention to become a signer of the stVaults Committee multisig with address 0xcD0cDa37f68a6758f86a4e2910E60174af1190B5.

Verification: Ethereum Verified Signed Message

1 Like

Hi!

I’d like to inform the community about my intention to become a signer of the stVaults Committee multisig with address 0x1555f8A94fC27A06C6610D00157216fa8783EA91.

Verification: Ethereum Verified Signed Message

1 Like

Hey there!
I’d like to inform the community about my intention to become a signer of the stVaults Committee multisig with address 0x21b82aa7149c8fd0562e78b740937442ffd43094.

Signed message

1 Like

Hello,

I’d like to inform the community about my intention to become a signer of the stVaults Committee multisig with address: 0xDbB7D7941d1340CB3ba862dF3A0f18084b5a69Ad

Signed message: Ethereum Verified Signed Message

1 Like

Hi everyone!

As per the feedback to allow parallel governance motions for tier upgrades and group share limit increases, the RegisterGroupsInOperatorGrid, RegisterTiersInOperatorGrid, and AlterTiersInOperatorGrid factories have been updated to remove the redundant tier.shareLimit <= group.shareLimit validation. This constraint is already enforced by OperatorGrid.onMintedShares() at minting time, so the factory-level check was causing unnecessary sequential dependencies between motions. Additionally, an explicit tier share limit bound check has been added to prevent uint96 overflow.

The updated implementations have been deployed:

Proposed items for the upcoming vote:

  1. Remove old RegisterGroupsInOperatorGrid factory 0xE73842AEbEC99Dacf2aAEec61409fD01A033f478 from Easy Track 0xF0211b7660680B49De1A7E9f25C65660F0a13Fea.

  2. Remove old RegisterTiersInOperatorGrid factory 0x5292A1284e4695B95C0840CF8ea25A818751C17F from Easy Track 0xF0211b7660680B49De1A7E9f25C65660F0a13Fea.

  3. Remove old AlterTiersInOperatorGrid factory 0x73f80240ad9363d5d3C5C3626953C351cA36Bfe9 from Easy Track 0xF0211b7660680B49De1A7E9f25C65660F0a13Fea.

  4. Add new RegisterGroupsInOperatorGrid factory 0x17305dB55c908e84C58BbDCa57258A7D1f7eEa7c to Easy Track 0xF0211b7660680B49De1A7E9f25C65660F0a13Fea (permissions: operatorGrid.registerGroup, operatorGrid.registerTiers 0xc69685e89cefc327b43b7234ac646451b27c544de37a7c0bc69685e89cefc327b43b7234ac646451b27c544d552b91da).

  5. Add new RegisterTiersInOperatorGrid factory 0x6b535F441F95046562406F4E2518D9AD7Db2dc0D to Easy Track 0xF0211b7660680B49De1A7E9f25C65660F0a13Fea (permissions: operatorGrid.registerTiers 0xc69685e89cefc327b43b7234ac646451b27c544d552b91da).

  6. Add new AlterTiersInOperatorGrid factory 0x37d9B09EDA477a84E3913fCB4d032EFb0BF9B62E to Easy Track 0xF0211b7660680B49De1A7E9f25C65660F0a13Fea (permissions: operatorGrid.alterTiers 0xc69685e89cefc327b43b7234ac646451b27c544d54544bcb).

Audit reports can be found here.

3 Likes

The on-chain vote #199 is now live and includes the proposal to upgrade stVaults Easy Track factories to register groups and register & alter tiers in Operator Grid.

The vote will be open for your “For” or “Against” input until the end of the main phase: Apr 11, 15:51 UTC.

For instructions on how to verify the vote items, please follow this guide.

2 Likes

The on-chain vote #199 passed and has been enacted. stVaults Easy Track factories to register groups and register & alter tiers in Operator Grid are now upgraded.