KVORUM
lidoSource: Snapshot · #0x0e8b53944051321d2cedf8881b546427bc6a22c9fe16f7d150af62fd837ff7da

Establish the stVaults Committee

succeededSep 29, 2025, 04:00 PM UTCsignaling · non-bindingby7F0x7fea…171bView on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

529 words

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 setup

Address: 0x18A1065c81b0Cc356F1b1C843ddd5E14e4AefffF

Signing threshold: 3/5

List of signers:

  • @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.

Note. 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.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters76
VP participating0
Outcome (current)Support
Current support—

06Voters

76 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bSupport022.08%—1y ago
420x42e6…3fb0Support017.30%—1y ago
810x8172…922eSupport09.26%—1y ago
7E0x7ee0…bb6cSupport08.66%—1y ago
LIlido.banteg.eth0x55bc…f0faSupport06.00%—1y ago
6D0x6d8d…0cccSupport05.79%—1y ago
9C0x9ca8…36afSupport05.43%—1y ago
510x510a…8d0eSupport05.22%—1y ago
AE0xae09…256bSupport03.98%—1y ago
3F0x3fb1…4c8aSupport02.88%—1y ago
A40xa418…b737Support02.17%—1y ago
B60xb664…f890Support02.14%—1y ago
6F0x6f9b…8a1dSupport02.12%—1y ago
1F0x1f76…5ed6Support01.75%—1y ago
390x3983…777aSupport01.21%—1y ago
7A0x7a59…8e22Support00.91%—1y ago
E80xe80e…28e8Support00.55%—1y ago
870x8787…ea52Support00.54%—1y ago
2C0x2cc1…4df1Support00.49%—1y ago
290x29b5…2c2fSupport00.27%—1y ago
100x10a2…36f3Support00.24%—1y ago
5D0x5df9…1b53Support00.24%—1y ago
3D0x3ddc…05b0Support00.19%—1y ago
980x9830…bd94Support00.14%—1y ago
060x06a9…bba0Support00.14%—1y ago
3D0x3d63…4afcSupport00.11%—1y ago
4D0x4d6c…5aaeSupport00.05%—1y ago
B90xb933…8dd1Support00.04%—1y ago
8A0x8a24…3e79Support00.03%—1y ago
960x96a7…a3b2Support00.02%—1y ago
B70xb792…89d7Support00.02%—1y ago
070x074c…3c82Support00.01%—1y ago
750x7526…b18eSupport00.01%—1y ago
8A0x8ab6…e0baSupport00.00%—1y ago
7A0x7af3…8df3Support00.00%—1y ago
F10xf19d…4865Support00.00%—1y ago
C50xc554…7759Support00.00%—1y ago
A70xa799…ddb0Support00.00%—1y ago
270x27d3…f70aSupport00.00%—1y ago
3D0x3d5a…b97fSupport00.00%—1y ago
050x0579…ca09Support00.00%—1y ago
020x0226…c730Support00.00%—1y ago
580x582c…0bf4Support00.00%—1y ago
D00xd072…59b3Support00.00%—1y ago
A10xa1ed…4bc4Support00.00%—1y ago
690x699a…80f9Support00.00%—1y ago
050x058e…d205Support00.00%—1y ago
790x795a…0310Reject00.00%—1y ago
900x9077…71cfSupport00.00%—1y ago
2C0x2cfa…c41eSupport00.00%—1y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.