KVORUM
lidoSource: Snapshot · #0xb4a35720b03f4c888c2fb41ab66ed324262d7a5b4696ffc3ee20bb35ebb0df6f

Rewards Share Committee Reform

succeededJan 26, 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

705 words

TL;DR

Reform and relaunch the Rewards Share Committee (”Committee”) as DAO-authorized operational committee to align with GOOSE-3 goals. This proposal updates the Committee mandate and process, including adding support of the stVaults which were introduced with Lido V3, as well as operational functions to help execute the changes approved to Curated Module processes, and updates Committee configuration. The full updated version of the Rewards Share Program is available on the Research Forum.

Background

  • The DAO approved the creation of the Committee in 2022 to support targeted rewards for Ethereum stake growth.[1]
  • Over time, the program evolved in naming and process, while its core goal stayed the same: targeted initiatives that seek to grow the adoption of stETH by fostering high-quality and secure ecosystem development.
  • Given the updated goals approved by the DAO via GOOSE-3 and the launch of Lido V3, the Rewards Share Committee should receive an update to its mandate, processes and configuration.

Proposal

The Committee will continue providing initiatives to support GOOSE-3 goals in stake growth within the Rewards Share Program. It is proposed to add two new functions to the original mandate: (1) manually paying Node Operator rebates and (2) supporting the operational execution of stVaults Rewards Share disbursements in accordance with the Reward Share Program 2026 (Revised). The changes in scope and process have been summarized below.

Node Operator Rebates

Following the Curated Module Fee Changes vote, to support near-term changes to the Curated Module V1 (CMv1) until the deployment and migration to Curated Module V2 (CMv2), a manual process is required to send rewards above the 3.5% Standard Operator reward rate to Node Operators in the Extra Effort and Client Team tiers. This manual processing of a portion of rewards would be necessary until the CMv2 migration is complete due to a technical limitation of CMv1. The Committee will be responsible for processing Node Operator reward allocation to Extra Effort and Client Team operators until this process is automated in CMv2.

stVaults

To support the Rewards Share Program in stVaults, this proposal expands Rewards Share activities to include stVaults.

Rewards share for stVaults will be determined (amounts and recipients) by the stVaults Committee. The stVaults Committee will provide the approved payout instructions the Rewards Share Committee for operational execution.

The Rewards Share Committee will be responsible for operationalizing payments, including disbursement from the Lido DAO Treasury to relevant recipients within the Committee's mandate and approved budget.

Budget & reporting

From 2026 onward, the Committee's budget for all activities is authorized via yearly EGG proposals submitted for approval to the DAO.

The Committee shall operate within the approved budget and mandate and shall report on these activities as part of the regular reports that the Lido Ecosystem Foundation files with the DAO.

Funds disbursement process

The Committee will use the same Easy Track setup to access stETH from the DAO Treasury, with a technical security limit of 3,000 stETH per year:

Rewards Share disbursements for NO Rebates and stVaults can either be made by adding the recipients to the Rewards Share Easy Track or directly from the Committee's multisig address only to execute approved Rewards Share payments within the Committee's mandate and budget.

Committee Configuration

To better reflect the current needs of the Committee, it is proposed:

  • to decrease quorum and number of participants from 4/8 to 3/5;

  • to establish the following Committee composition:

    ParticipantAddressNew / Existing Participant
    Pipistrella0x5da409e1cbDABeC67471dB01Ff956f804bb8879fExisting
    K_G0xC0DB9e34A47Ba42B6C17E6adae8f07d1Cb37C3d5Existing
    Alex_L0xb339918e75664a07bb650513427559920c0a0f6cExisting
    Armin0x8ecd93982FfbB2f937ADa6c6e50d1950974081C0New
    Willem H0x28939ef21690Fe8358E93d661d1ce6d7fA9154F3New
    • Departing participants: adcv, robingop, skelkneko, zuzu_eeka

Signers act as committee participants for operational execution and do not represent or bind the DAO outside the DAO-approved mandate.

Next Steps

If the Snapshot vote passes, the updated version of the Rewards Share Program incorporating the described changes for the NO Rebates and stVaults, will be adopted, and the Rewards Share Committee will undergo a signer rotation, with updated threshold and quorum parameters.

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

Voters106
VP participating0
Outcome (current)For
Current support100%

06Voters

106 total
Filter:
VoterChoice% of totalRationale
420x42e6…3fb0For017.26%—10mo ago
4A0x4af8…6a0bFor016.49%—10mo ago
6C0x6cd6…b52eFor013.10%—10mo ago
810x8172…922eFor09.83%—10mo ago
7E0x7ee0…bb6cFor09.19%—10mo ago
LIlido.banteg.eth0x55bc…f0faFor06.37%—10mo ago
9C0x9ca8…36afFor05.76%—10mo ago
AE0xae09…256bFor04.22%—10mo ago
6D0x6d8d…0cccFor03.29%—10mo ago
3F0x3fb1…4c8aFor03.06%—10mo ago
6F0x6f9b…8a1dFor02.87%—10mo ago
B60xb664…f890For02.22%—10mo ago
310x3133…5c00For02.10%—10mo ago
A40xa418…b737For01.83%—10mo ago
1F0x1f76…5ed6For00.89%—10mo ago
E80xe80e…28e8For00.42%—10mo ago
9C0x9cbc…7519For00.31%—10mo ago
060x06a9…bba0For00.21%—10mo ago
360x36f7…a589For00.15%—10mo ago
390x3940…a5fcFor00.15%—10mo ago
3D0x3ddc…05b0For00.10%—10mo ago
8E0x8e18…8c7bFor00.06%—10mo ago
B90xb933…8dd1For00.06%—10mo ago
5F0x5fdc…b69fFor00.05%—10mo ago
440x442d…44afFor00.01%—10mo ago
C50xc554…7759For00.00%—10mo ago
3A0x3a5c…ca89For00.00%—10mo ago
050x0579…ca09For00.00%—10mo ago
3D0x3d5a…b97fFor00.00%—10mo ago
1D0x1d71…b6b0For00.00%—10mo ago
A90xa9bf…1577For00.00%—10mo ago
B10xb1f8…4250For00.00%—10mo ago
F80xf804…9d2eFor00.00%—10mo ago
CC0xcc44…dc23For00.00%—10mo ago
640x6409…8590For00.00%—10mo ago
050x058e…d205For00.00%—10mo ago
D90xd929…5e47For00.00%—10mo ago
100x10e3…b4a7For00.00%—10mo ago
EB0xebc9…7013For00.00%—10mo ago
A70xa7b5…49f2For00.00%—10mo ago
B90xb93e…02fcFor00.00%—10mo ago
BF0xbff4…030fFor00.00%—10mo ago
A00xa0c3…d7b5For00.00%—10mo ago
500x500f…7d0bFor00.00%—10mo ago
4D0x4d32…bbfaFor00.00%—10mo ago
170x1729…b879For00.00%—9mo ago
9D0x9d57…65a5For00.00%—10mo ago
2F0x2f2f…f78aFor00.00%—10mo ago
B30xb3bf…6ce4For00.00%—10mo ago
AF0xaf90…7b3bFor00.00%—10mo ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.