# Proposal to form reWARDS Committee

**URL:** <https://research.lido.fi/t/proposal-to-form-rewards-committee/1447>\
**Category:** Proposals\
**Created:** [December 2, 2021, 10:00pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447 "2021-12-02T22:00:10Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbeezy](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jbeezy](https://research.lido.fi/u/jbeezy)\
**Post date:** [December 2, 2021, 10:00pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/1 "2021-12-02T22:00:10Z")

</div>

## Proposal to form reWARDS Committee

We are renewing our focus on policy & governance at Lido, and are asking the community (we need a name) to discuss and vote on a rewards committee. As we get used to proposing more of these structures, a framework will be needed to standardize the process going forward.

Lido is a DAO. DAOs are by definition supposed to be decentralized. It is paramount the community behind a DAO increasingly make all key decisions. However, as a DAO grows and becomes complex, there will be an increased need to delegate minor or highly specialized tasks to reduce operational burden. This way, we hope to reduce voter fatigue on matters they might lack the time, interest or technical expertise to carefully consider.

All DAOs face this challenge. A balance between direct community involvement and delegating responsibilities.

There will be a snapshot vote 3 days after posting or when community discussion has resolved to an optimal outcome.

Thanks in advance for reading and commenting on the rewards committee proposal.

### Summary

Create a governance committee dedicated to managing, deploying, tracking and reporting incentives for Lido assets.

Allow the committee autonomy to deploy allocated rewards budget as they see fit with monthly reporting on the decision-making process and community feedback. There will be broad categories around each of the initiatives as well such as ‘maintain liquidity’, ‘increase usage in DeFi’, ‘facilitate trading volume’ etc. These will come with category breakdowns.

### Motivation

Currently Lido is allocating ~$15M(USD) $LDO rewards across a number of different pools each month with more coming online. The current process is cumbersome and lacks proper clarity on the efficacy of the programs.

Sushi, 1inch, Curve, Balancer, Saber, Raydium, Mercuial and Orca. These are only AMMs. There will be additional needs to allocate incentives to lending platforms, aggregators, new DeFi protocols and new ecosystems as we increase our integrations.

The current process requires a community proposal to add new incentives to a pool, snapshot vote to pass, and then on-chain voting to disburse the funds.

This is slow at times while also increasing voter fatigue in governance.

The weekly Omnibus was a great first step of bundling operational expenses into a single vote. After this came [LIP-3 Easy Track Motions](https://research.lido.fi/t/lip-3-easy-track-motions-for-dao-routine-operations/680) to streamline routine voting decisions which this proposal will build on top of once fully implemented.

### Proposal

I propose a founding committee of current members already working on the rewards distribution and a member from the community to start. Later it might be prudent to have a representative from each protocol Lido is built on added (this might become burdensome).

**Proposed starting wards**

- jbeezy from Lido, business development
- GrStepanov from Lido, has been managing technical integrations
- kadmil from Lido, has been managing incentives and on-chain omnibus
- Alex Beckett from community, has been an active and engaged supporter
- Felix from Chorus One, managing stSOL go to market
- Kai, currently building stLuna for Terra

**Governance**

The reWARDS committee should be considered part of the Financial Operations Team along with the LEGO committee. The Financial Team will be proposed at a future date.

Use of Easy Track [Rewards Executors](https://research.lido.fi/t/lip-3-easy-track-motions-for-dao-routine-operations/680#rewards-easy-track-executors-9) to initiate funds. This guarantees rewards are only sent to whitelisted addresses ensuring all funds are accounted for.

All new whitelisted addresses are voted on by the committee before being added. Initial candidates are listed below in breakdown. All whitelisted addresses eligible for rewards are listed along with corresponding amounts in the monthly report.

Rewards distribution will start with 4/6 signatures and move to a higher security threshold with new members within 3 months.

**Accountability**

At the end of each month, the committee will publish a report on locations, amount and efficacy of incentives for each platform distributed. This report will also request a tentative budget for the following month in $LDO to be allocated as they see fit within that budget and with community feedback taken into consideration on each reporting period.

A reporting period will be 3 days of community feedback followed by a snapshot vote only if feedback is contentious or changes outcomes.

The $LDO will be managed by a public multi-sig controlled by the wards without the need to actually hold them.

With easy track the multi-sig wallet is able to pull funds out as needed and can only send them to approve whitelisted addresses.

**Change Management**

I propose an initial committee member review within the first 6 months pending proposal approval to discuss change management and/or areas for improvement.

**Initial Budget**

Due to specifically how easy tracks works there is not a ‘real’ cap on budget but accountability and oversight will ensure the committee is not sending excessive funds to a whitelisted address.

For Solana addresses, there is a slightly different process due to the bridging via Wormhole so the ETH side address will be whitelisted to start.

6,000,000 $LDO is the proposed budget for the first calendar month following a successful vote. This allows for room to grow incentives and flexibility for unknowns.

The additional ~1,800,000 LDO over current spend is earmarked for expansion of rewards on Solana with the addition of new pools and protocols. This will be accounted for and added to the whitelist as they come online pending approval of the whitelist additions.

### Breakdown and starting whitelist

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/1X/68e1e7ab775cdf13ba2e99548b20536963d05e88.png)

[LDO Incentives dashboard on Dune](https://dune.xyz/LidoAnalytical/LDO-incentives)

### Benefits to Lido

- Streamline routine voting around the rewards program which is a critical part of Lido strategy
- Increase transparency about efficiency of the rewards program with reporting
- Lower the operating overhead for initiating new rewards or continuing existing ones
- Allow flexibility to try new rewards strategies
- Increase community feedback
- Decrease spend on lower utilization pools

### Related Threads

> [@Rewards Committee composition for Easy Track](https://research.lido.fi/t/rewards-committee-composition-for-easy-track/1442):
>
> Easy Track: The Rewards Committee composition The Omnibus voting to enable Easy Track [has been started](https://mainnet.lido.fi/#/lido-dao/0x2e59a20f205bb85a89c53f1936454680651e618e/vote/103/). If passed, two roles will be granted to the EVMScriptExecutor smart contract: ‘CREATE\_PAYMENTS\_ROLE’ to allow LEGO committee and Rewards Committee to handle fund allocations (top-up LEGO program and top-up whitelisted reward programs); ‘SET\_NODE\_OPERATOR\_LIMIT\_ROLE’ to allow node operators to increase their staking limits. In the [Easy Track release announcement post](https://research.lido.fi/t/lip-3-easy-track-release/1406) we have mentioned the Re…

> [@Continue Curve and Sushi LP rewards](https://research.lido.fi/t/continue-curve-and-sushi-lp-rewards/1436):
>
> By mid-December, the 30-days reward periods both for Curve stETH/ETH and Sushi wstETH/DAI liquidity pools will expire (on 11th and 16th of December respectively). Curve stETH/ETH LP rewards For almost a year, Curve pool used to be the foothold of stETH/ETH peg and keeps maintaining it steadily. It’s also the deepest pool across DeFi at around $5 billion TVL at the moment. Keeping it stable and safe is of paramount importance to the protocol, so we propose continuing the LP rewards with the same…

> [@Continue LDO rewards for 1inch stETH\<\>DAI LP](https://research.lido.fi/t/continue-ldo-rewards-for-1inch-steth-dai-lp/1372):
>
> The second 30-days period of 1inch stETH\<\>DAI LP rewards is set to expire on November 24th. The second period of rewards for the 1inch stETH\<\>DAI liquidity pool was different from the first one. Since it has only been incentivized with 200,000 LDO (and not with 200,000 1INCH), we expected it to lose some TVL over its second month, and that is what essentially happened – the pool has lost half of its liquidity and stabilized at around $33mil TVL. Pool APY is currently around 35%, and it still ap…

> [@Continue LP rewards for Sushi DAI\<\>wstETH pool](https://research.lido.fi/t/continue-lp-rewards-for-sushi-dai-wsteth-pool/1365):
>
> LP rewards for Sushi DAI\<\>wstETH liquidity pool are set to expire on November 16th. It’s time to decide on what would be the next month of this pool in terms of LDO incentives. From [analytical dashboard](https://dune.xyz/LidoAnalytical/Sushi-DAI-wstETH) it looks like the pool is operating normally. Pool TVL was relatively steady over the past 30-days period except for one significant withdrawal of around $10m on October 29th. However, TVL decrease is not unexpected at current ETH price fluctuations, because the assets in the pool are exposed t…

---

<div class="post-metadata">

**Author:** ![PatrickOD](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/patrickod/32/788_2.png) [@PatrickOD](https://research.lido.fi/u/PatrickOD)\
**Post date:** [December 3, 2021, 12:49am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/2 "2021-12-03T00:49:00Z")

</div>

This is awesome to see. I think this will be a big step forward in decentralizing the DAO, and in getting more of the decision making process out into the open to draw in more input.

I had a few questions, some of which are probably due to me not being super familiar with Easy Track yet so sorry if that is the case…

Is it right that the only functions of the rewards committee that go through the Easy Track process are the actual movements of funds? And any other decision making (budgeting, changes to committee members, whitelisting, etc) would take place outside of it? And would those transfers be proposed as “Motions” in Easy Track?

Why is it that Easy Track doesn’t allow for a hard budget cap? Is there any hard limit on this proposed committee’s ability to send funds from treasury anywhere in the code (Easy Track or otherwise)? or is it just the ability to object to a payment Motion or pull the emergency brake on Easy Track in an extreme case?

Realizing that most of my questions revolve around whether objecting to a Motion for a given payment in Easy Track is the only enforcement mechanism that the rest of the DAO would have other than revoking privileges through the main governance process.

---

<div class="post-metadata">

**Author:** ![vsh](https://avatars.discourse-cdn.com/v4/letter/v/b19c9b/32.png) [@vsh](https://research.lido.fi/u/vsh)\
**Post date:** [December 3, 2021, 7:49am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/3 "2021-12-03T07:49:32Z")

</div>

> Is it right that the only functions of the rewards committee that go through the Easy Track process are the actual movements of funds? And any other decision making (budgeting, changes to committee members, whitelisting, etc) would take place outside of it? And would those transfers be proposed as “Motions” in Easy Track?

Transfers of funds and managing of rewards program whitelist will also be through easy track. The list of addresses where the rewards committee can send funds is limited, and managing it is also done through ET motions.

> Why is it that Easy Track doesn’t allow for a hard budget cap? Is there any hard limit on this proposed committee’s ability to send funds from treasury anywhere in the code (Easy Track or otherwise)? or is it just the ability to object to a payment Motion or pull the emergency brake on Easy Track in an extreme case?

The reason is we didn’t put it into a v1 release to avoid dragging it further down the road. It’s in the backlog, will be in one of the next upgrades (no timeline on this yet).

The relatively gated structure of easy tracks + the easiness to shut down a malicious notion are together an adequate safeguard IMO, and, from the looks of it, in DAO’s eyes as well.

---

<div class="post-metadata">

**Author:** ![GrStepanov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/grstepanov/32/254_2.png) [@GrStepanov](https://research.lido.fi/u/GrStepanov)\
**Post date:** [December 3, 2021, 8:57am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/4 "2021-12-03T08:57:20Z")

</div>

Thank you @jbeezy for nominating me, I hope I will be able to provide valuable input ✌🏾  
I believe the most important thing the Committee can do is streamline reports and proposals for the whole complex of Lido’s incentives. The monthly report+proposal can provide a great vision of how, what, and why we incentivize. It looks very natural to grant the Committee rights to start ET motions related to incentives as well.  
On the other hand, adding more DAO votings – even snapshot ones – to decide on proposed incentives doesn’t sound reasonable to me. That is something we were trying to avoid when designing the Easy Track – we tried to remove regular Aragon votings where possible while keeping a clear and easy way to object to anything that doesn’t look good. I propose sticking with this approach and generally using the Committee for two things:

1. Report and propose: publish monthly analytics on incentives performance and propose changes for the next month.
2. Maintain rewards-related Easy Track process: manage reward programs whitelist and initiate funds allocations.

---

<div class="post-metadata">

**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\
**Post date:** [December 3, 2021, 9:00am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/5 "2021-12-03T09:00:26Z")

</div>

I’m all pro using snapshots for the DAO to decide on contentious issues with incentives — that seems like a most suitable mechanics there. If the plan for the next month doesn’t get pushback — reWARDS can just schedule & send motions required to carry the plan on.

---

<div class="post-metadata">

**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\
**Post date:** [December 3, 2021, 9:08am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/6 "2021-12-03T09:08:26Z")

</div>

Thank you for nominating me, @jbeezy!  
I think that: 1) the overall structure on the incentive management is a great thing to have; 2) having dedicated & public team working on those is fully in the spirit of transparency, which seems the most appropriate; 3) having defined & public workflow around incentives seems cool as well.

---

<div class="post-metadata">

**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\
**Post date:** [December 3, 2021, 9:08am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/7 "2021-12-03T09:08:40Z")

</div>

Should we define Terra budget here as well?

---

<div class="post-metadata">

**Author:** ![vsh](https://avatars.discourse-cdn.com/v4/letter/v/b19c9b/32.png) [@vsh](https://research.lido.fi/u/vsh)\
**Post date:** [December 3, 2021, 10:20am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/8 "2021-12-03T10:20:23Z")

</div>

I think so, yes, and further stX products as well.

---

<div class="post-metadata">

**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\
**Post date:** [December 3, 2021, 10:26am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/9 "2021-12-03T10:26:16Z")

</div>

I mean, from the get-go — I think it makes total sense to manage all the incentives with one process & team, having “network experts” on board (Felix on Solana and Kai on Terra, per the proposal).

---

<div class="post-metadata">

**Author:** ![jbeezy](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jbeezy](https://research.lido.fi/u/jbeezy)\
**Post date:** [December 3, 2021, 6:37pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/10 "2021-12-03T18:37:57Z")

</div>

@GrStepanov @kadmil I think those are great suggestions to remove the additional snapshot vote except in case of disputes. Before the snapshot vote on this I will update the proposal with that modification.

Regarding additional listings with the additional budget, I had not defined those in this proposal as they are outside the scope imo. This is to stand up and agree on the committee itself due to variable timelines related to the easy track and this proposal passing.

If executed, the first priority would be defining expected use of funds for the first operating month. Across ecosystems.

I am happy to add additional committee members if that is the community feedback. Trying to balance operational overhead to get this moving. If agreed upon I will add that prior to the snapshot as well.

---

<div class="post-metadata">

**Author:** ![jbeezy](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jbeezy](https://research.lido.fi/u/jbeezy)\
**Post date:** [December 5, 2021, 8:11pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/11 "2021-12-05T20:11:28Z")

</div>

Proposal has been updated with previous suggestions to remove additional snapshot vote unless monthly reports are contentious as well as adding Felix and Kai as wards. The multi-sig threshold was increased to 4/6.

[Snapshot vote](https://snapshot.org/#/lido-snapshot.eth/proposal/0xe565ad27e1beaacbe0e68bec59bd3d86a80d669ca80022b76dc31be697f6e078) will be live in 20 minutes.

For: Create the committee  
Against: Do not create the committee at this time. Continue the discussion or modification of this proposal.

---

<div class="post-metadata">

**Author:** ![GrStepanov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/grstepanov/32/254_2.png) [@GrStepanov](https://research.lido.fi/u/GrStepanov)\
**Post date:** [December 9, 2021, 8:33am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/12 "2021-12-09T08:33:52Z")

</div>

[The snapshot vote](https://snapshot.org/#/lido-snapshot.eth/proposal/0xe565ad27e1beaacbe0e68bec59bd3d86a80d669ca80022b76dc31be697f6e078) is over and passed! Thank you.  
One of the next steps will be putting together a 4/6 reWARDS Committee multi-sig, it will be announced publicly as soon as possible.  
Another one is the first planning session, the Committee will keep the community posted on the results. We hope to see a live discussion around it soon!

---

<div class="post-metadata">

**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\
**Post date:** [December 13, 2021, 8:55am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/13 "2021-12-13T08:55:37Z")

</div>

The reWARDS multisig is successfully set up as 4/6 [0x87D93d9B2C672bf9c9642d853a8682546a5012B5](https://gnosis-safe.io/app/eth:0x87D93d9B2C672bf9c9642d853a8682546a5012B5/)!

Members are:

jbeezy `0x039bDD285d3eDb1D9B6001d3097067Aa2AF7d826` [https://twitter.com/chaingenius/status/1468951124841570304](https://twitter.com/chaingenius/status/1468951124841570304)

GrStepanov `0x8D0855047b59a5f11262f095ee724b5A59a89710` [https://twitter.com/grstepanov/status/1468933222923116550](https://twitter.com/grstepanov/status/1468933222923116550)

kadmil `0x9A3f38AF97b791C85c043D46a64f56f87E0283D4` [https://twitter.com/victor\_suzdalev/status/1468934248417705987](https://twitter.com/victor_suzdalev/status/1468934248417705987)

Alex Beckett `0xbD04aA2eD46Df0c8d547A16E29288A960CaE72f5` [https://twitter.com/likebeckett/status/1469132266093772801](https://twitter.com/likebeckett/status/1469132266093772801)

Felix `0x7EA5D688f0aaEBce7d094D18f2C570a83A4d76Cc` [https://twitter.com/FelixLts/status/1468932706797031435](https://twitter.com/FelixLts/status/1468932706797031435)

Kai `0xC5bfE99909c982a8F01762632226F34AAf96bA86` [https://twitter.com/oldremez/status/1468942529332719616](https://twitter.com/oldremez/status/1468942529332719616)

The multisig would be able to start Easy Track motions to whitelist rewards programms addresses or remove those from the whitelist, as well as sending funds to those addresses.

---

<div class="post-metadata">

**Author:** ![alexbeckett](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/alexbeckett/32/819_2.png) [@alexbeckett](https://research.lido.fi/u/alexbeckett)\
**Post date:** [December 21, 2021, 8:20am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/14 "2021-12-21T08:20:32Z")

</div>

I am resigning from my position on the rewards committee. I wish the team the best and look forward to seeing the Lido’s continual growth in the future.

---

<div class="post-metadata">

**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\
**Post date:** [December 22, 2021, 1:40pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/15 "2021-12-22T13:40:24Z")

</div>

Thank you for participation!

---

<div class="post-metadata">

**Author:** ![18519865qwe](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/18519865qwe/32/727_2.png) [@18519865qwe](https://research.lido.fi/u/18519865qwe)\
**Post date:** [December 23, 2021, 4:22am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/16 "2021-12-23T04:22:40Z")

</div>

Should the Chinese-speaking community also have one member?

---

<div class="post-metadata">

**Author:** ![jbeezy](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jbeezy](https://research.lido.fi/u/jbeezy)\
**Post date:** [December 27, 2021, 6:38pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/17 "2021-12-27T18:38:26Z")

</div>

We are happy to discuss new member additions in the next 1-2 months once we are a bit more structured. The only requirement is someone who has been active in the community and will be available to meet the demand for workload.

---

<div class="post-metadata">

**Author:** ![vsh](https://avatars.discourse-cdn.com/v4/letter/v/b19c9b/32.png) [@vsh](https://research.lido.fi/u/vsh)\
**Post date:** [January 3, 2022, 2:24pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/18 "2022-01-03T14:24:18Z")

</div>

Sorry to hear that! Would love to have you on board in this or other capacity if you’ve got more time to spend.

---

<div class="post-metadata">

**Author:** ![Ivan](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ivan/32/840_2.png) [@Ivan](https://research.lido.fi/u/Ivan)\
**Post date:** [May 4, 2022, 3:55pm UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/19 "2022-05-04T15:55:21Z")

</div>

Due to transition of the Lido on Solana project from Chorus One to the P2P team we suggest changes in a team of Lido Rewards Committee.  
Ivan Manvelov(from Lido on Solana team) will take place instead of Felix Lutsch (Chorus One team member) to manage the process of rewards distribution on Solana chain.

The following address to use for Solana Multisig : AHGCPfBJ1jm8xaoYjBQX1tQ8Qcevs3PQnXQrvgRhv1xd

Ethereum address:  
0x6c2f2ac02517e3E6Ede7cf3dd5970c428aF4bfb3

> <https://twitter.com/imanvelov/status/1521870564838813697?s=20&t=GN2kf50hMvrGQQz5grhykg>

---

<div class="post-metadata">

**Author:** ![jbeezy](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jbeezy](https://research.lido.fi/u/jbeezy)\
**Post date:** [May 9, 2022, 11:42am UTC](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447/20 "2022-05-09T11:42:11Z")

</div>

I am rotating my Solana rewards multisig key from 6rwjQTzepxgABYggM3CNAyjkbyaGiU7Kjtm2kbgyS3rG  
to  
GceE1hF9PYBu3ABuadeab1xE5y4bPgRcCSGchCDoU175

> <https://twitter.com/chaingenius/status/1523629060915888128?s=20&t=Wgw5C6NUZKqPTMsK8Rnc2Q>

[Next page](https://research.lido.fi/t/proposal-to-form-rewards-committee/1447.md?page=2)
