KVORUM
lidoSource: Snapshot · #0x60cfe3531cd13ab84f5f6aaef7bcaab1747cbea4544dc7d18daaf642e36c9d39

Redirect DVT & APM Incentives to Current Meta Treasury and LoL

succeededApr 13, 2026, 04:00 PM UTCsignaling · non-bindingbyFF0xff64…1fceView on Snapshot ↗

01Summary

AISummary by Kvorum

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

02Description

553 words

Proposal Summary

This proposal aims to formalize the change in destination and utilization of post-Node Operator share of DVT incentives and APM incentives flows, and seeks DAO approval to:

  • Redirect post-Node Operator share of DVT incentives flow arising from Obol and SSV Network providers (allocated under the recently approved terms) from the Decentralized Validator Vault to the Lido Earn Current Meta Treasury multisig to support Lido Earn ETH vault strategies.
  • Route APM incentives flow to the Liquidity Observation Lab multisig to make them available to the Growth Committee for agile deployment and continuous support of liquidity-focused strategies that contribute to the overall health of the stETH ecosystem.

DVT Incentives

The Decentralized Validator Vault (DVV), implemented by Mellow, was launched in August 2024 as a coordination layer for user stake and Distributed Validator Technology (DVT) provider incentives. Among its primary goals was providing DVV stakers with access to Obol and SSV Network incentive programs they could not access directly.

Under the current setup, user deposits of ETH or WETH are staked via the Lido protocol and channeled to DVT-supporting modules. In return, users receive DVstETH tokens representing their share in the DVV, along with additional DVT-specific rewards such as Obol contributions and SSV Incentivized Mainnet Program (IMP) incentives.

The launch of Lido Earn ETH vault has materially changed the DVV's role. Lido Earn ETH provides a unified interface for vault stakers to access curated reward strategies and now includes the Mellow DVV as one of the sub-vaults. With this shift, the DVV's function as a standalone DVT incentive coordination mechanism is effectively absorbed into a more scalable Earn architecture.

It is proposed to replace DVV’s coordination role with Lido Earn by redirecting and consolidating the DVV staker-directed (post-Node Operator) share of DVT incentives to the Lido Earn Current Meta Treasury multisig 0xcCf2daba8Bb04a232a2fDA0D01010D4EF6C69B85. This will allow to reduce governance overhead while ensuring DVT-derived rewards continue to benefit Earn participants without interruption.

APM Incentives

Last year, contributors to the Lido protocol introduced the APM framework to establish an operational framework around an emerging class of proposer-layer innovations and sidecars. In May 2025, the Lido DAO approved the establishment of the APM Committee to provide structured governance and oversight over these mechanisms. However, while the APM Committee is responsible for evaluating and approving the use of APMs, it has not been given a mandate or the operational tools to manage APM incentive flow.

APM-derived incentives (including but not limited to, for example, Primev) differ materially from DVT incentives: they are more variable, execution-layer–driven, market-sensitive, and often require more agile and market-aware decision-making. The Growth Committee is well-positioned to oversee these incentives, given its mandate to drive stETH adoption, liquidity depth, and ecosystem expansion.

Building on this, the APM incentives flow is proposed to be routed to Liquidity Observation Lab multisig 0x87D93d9B2C672bf9c9642d853a8682546a5012B5 operating under the Growth Committee. This would enable more agile, data-driven deployment of incentives and enable the Growth Committee to continuously support liquidity-focused strategies within its existing mandate.

Next steps

If the proposal is approved:

  • Post-Node Operator share of DVT incentives flow will be redirected to the Lido Earn Current Meta Treasury multisig, and DVV will no longer act as an incentive coordination layer.
  • APM incentives flow will be routed to the Growth Committee’s Liquidity Observation Lab multisig.

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

Voters56
VP participating0
Outcome (current)Support
Current support—

06Voters

56 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bSupport015.59%—7mo ago
420x42e6…3fb0Support013.66%—7mo ago
6C0x6cd6…b52eSupport012.39%—7mo ago
B60xb664…f890Support010.82%—7mo ago
A40xa418…b737Support010.42%—7mo ago
1F0x1f76…5ed6Support09.31%—7mo ago
810x8172…922eSupport09.29%—7mo ago
LIlido.banteg.eth0x55bc…f0faSupport06.02%—7mo ago
450x45bc…fd99Support03.54%—7mo ago
6D0x6d8d…0cccSupport02.90%—7mo ago
6F0x6f9b…8a1dSupport02.74%—7mo ago
310x3133…5c00Support02.07%—7mo ago
E80xe80e…28e8Support00.39%—7mo ago
9C0x9cbc…7519Support00.27%—7mo ago
060x06a9…bba0Support00.20%—7mo ago
360x36f7…a589Support00.14%—7mo ago
3D0x3ddc…05b0Support00.11%—7mo ago
3D0x3d63…4afcSupport00.07%—7mo ago
B90xb933…8dd1Support00.05%—7mo ago
390x3940…a5fcSupport00.00%—7mo ago
3D0x3d5a…b97fSupport00.00%—7mo ago
F80xf804…9d2eSupport00.00%—7mo ago
F10xf1cc…ac93Support00.00%—7mo ago
B10xb1f8…4250Support00.00%—7mo ago
640x6409…8590Support00.00%—7mo ago
FD0xfde2…c13cSupport00.00%—7mo ago
8E0x8e18…8c7bSupport00.00%—7mo ago
1D0x1d71…b6b0Support00.00%—7mo ago
A90xa9bf…1577Support00.00%—7mo ago
9C0x9c9a…bc0cSupport00.00%—7mo ago
D90xd929…5e47Support00.00%—7mo ago
100x10e3…b4a7Support00.00%—7mo ago
A70xa7b5…49f2Support00.00%—7mo ago
B90xb93e…02fcSupport00.00%—7mo ago
170x1729…b879Support00.00%—7mo ago
870x87c7…7960Support00.00%—7mo ago
0D0x0df5…105dReject00.00%—7mo ago
9D0x9d57…65a5Support00.00%—7mo ago
4D0x4d32…bbfaSupport00.00%—7mo ago
1F0x1f3d…0591Support00.00%—7mo ago
2F0x2f2f…f78aSupport00.00%—7mo ago
B30xb3bf…6ce4Support00.00%—7mo ago
BF0xbfd1…4f66Support00.00%—7mo ago
650x659f…dadcSupport00.00%—7mo ago
AF0xaf90…7b3bSupport00.00%—7mo ago
010x0151…c3b9Support00.00%—7mo ago
CE0xce57…70f0Support00.00%—7mo ago
3F0x3fb1…4c8aSupport00.00%—7mo ago
340x3426…5404Support00.00%—7mo ago
4D0x4d4a…1bdfSupport00.00%—7mo ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.