# Pol Lanski Delegate Thread

**URL:** <https://research.lido.fi/t/pol-lanski-delegate-thread/8155>\
**Category:** Delegate Platform\
**Created:** [August 19, 2024, 2:20pm UTC](https://research.lido.fi/t/pol-lanski-delegate-thread/8155 "2024-08-19T14:20:55Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Lanski](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/lanski/32/4846_2.png) [@Lanski](https://research.lido.fi/u/Lanski)\
**Post date:** [December 18, 2024, 2:40pm UTC](https://research.lido.fi/t/pol-lanski-delegate-thread/8155/11 "2024-12-18T14:40:09Z")

</div>

After engaging in another round of discussions in the forum, I feel we’re getting into a rhythm where delegates are being listened to and more actively participating in shaping the proposals.

I’ll include links to the relevant discussions when available.

# 1. [CSM: Enable Permissionless Phase and Increase the Share Limit](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7cbd5e9cb95bda9581831daf8b0e72d1ad0b068d2cbd3bda2a2f6ae378464f26)

Forum post [here](https://research.lido.fi/t/community-staking-module/5917/83)

### Vote: **For**

### Rationale:

The continuation and closing of the initial deployment stage of the CSM saga. This culminates years of work. I’ve discussed this with Eugene years ago, at one ETHCC, for the first time, and it now becomes permissionless. Very proud of what the CSM team has achieved.

Specifically, this proposal suggests:

1. Ending the Early Access phase and going into full permissionless mode, meaning everyone will be able to participate.
2. Increase the share of Lido Protocol ETH allocated to CSM from 1% to 2%.

This means open season for everyone to participate to CSM, plus more ETH flowing into the module. Time to do so.

I have [voiced my concerns](https://research.lido.fi/t/community-staking-module/5917/83) that full permissionlessness could attract big players / whales / institutional, as it provides a way to leverage ETH better than solo staking. I think this is one of the limitations of the CSM. If it indeed gets captured, another module can be spun up, or another vote for changing the conditions for CSM to make it truly “Community” - if it had stopped being so- could be had. Forward with CSM!

# 2. [Lido Alliance Grant Proposal](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7569e4487b7737fa8e98fe708843deb014a61d0dbfeeb6e57ad1f4dba5494598)

Forum post [here](https://research.lido.fi/t/egg-lido-alliance-grant-funding/9068)

### Vote: **For**

### Rationale:

The Lido Alliance has onboarded 3 projects so far, Drop, Mellow and Bolt. I am on the fence with Drop, but I think Mellow and Bolt have a very direct link on the ecosystem, and have existing products (see [Mellow’s Decentralized Validator Vault](https://app.mellow.finance/vaults/ethereum-dvsteth)) or future products that will be key in the future of Ethereum and Staking, as it’s the case of Bolt’s preconf protocol.  
Based on these results, I am keen on keeping the Lido Alliance alive and to onboard more projects onto it.

# 3. [[EGG] Multi-EGG Continuity Grant Funding](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8736420fd3ebecc1aae603c3a49d6805899c38b142c92525169e5bfa95f53b26)

Forum post [here](https://research.lido.fi/t/egg-multi-egg-continuity-grant-funding/9067)

### Vote: **For**

### Rationale:

This proposal combines 3 main funding verticals:

1. A “bridge” budget for **3 mo** and `11M DAI` for Governance and CSM teams to deliver on Dual Governance and on the permissionless CSM. These are considered GOOSE (v1) goals and not yet GOOSEv2, which was just approved by the DAO - I voted for them. Hence, the budget will last 3m and another EGG to deliver on the GOOSEv2 can be expected to be proposed by Pool Maintenance and Argos and RCC, the structures that are involved in the delivery.  
“A bridge budget for old objectives?!” I hear you say. Fret not, this is most likely not even extra money, as [st2024v2](https://research.lido.fi/t/egg-st2024-v2-continuity-grant-funding-to-achieve-goose-goals/7697), the previous EGG tackling these goals, is underspent. While we don’t know the final numbers of st2014v2, it is likely that the final cost will be what was approved without the bridge budget, or within acceptable parametres.

2. The second EGG, for **6mo** and for a `8.5M DAI` would be to **incentivize liquidity** and experiment and research on this topic. Best-before date: 2025/06/30

3. 3rd EGG, for **the whole 2025** would cover the Bug Bounty program and budget `2M DAI`. They will be budgeted, but only drawn in case of a payout event.

TBH, most of my time analysing this proposal was spent trying to understand the relationship between 1. Pool Maintenance Labs Ltd, 2. Argo Technology Consulting Ltd and 3. the [RCC](https://research.lido.fi/t/lido-v2-may-1-2023-december-31-2023-lido-ongoing-grant-request/) (Resourcing and Compensation Committee); and figuring out that it was indeed an extension on st2014v2 for the **3 mo** piece.

A lot of [good discussion was had](https://research.lido.fi/t/egg-multi-egg-continuity-grant-funding/9067/12) on making this more obvious because transparency means clarity too, as a lot can be hidden through obfuscation (although I don’t believe this situation was created on purpose). I asked for “deliverable” transparency and not only “economic” transparency, which @steakhouse provides, although it’s more of a long term goal to facilitate these discussions and make them more agile.

# 4. [Extend On-Chain Voting Duration](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xa58da73cc4257837ae981d8ad861252f4cbbda7a173a577702f8f93561f57825)

Forum post [here](https://research.lido.fi/t/optimizing-lido-on-chain-voting-timelines-for-inclusive-governance/8265)

### Vote: **Extend duration to 3+2 days**

### Rationale:

My position is captured on the [forum thread](https://research.lido.fi/t/optimizing-lido-on-chain-voting-timelines-for-inclusive-governance/8265/25) discussing the initiative:

> [@Optimizing Lido On-chain Voting Timelines for Inclusive Governance](https://research.lido.fi/t/optimizing-lido-on-chain-voting-timelines-for-inclusive-governance/8265/25):
>
> For me, there are 2 important points:
> 
> - Quorum should be reached, and it’s disappointing that it doesn’t some times: [Lido DAO Voting UI](https://vote.lido.fi/vote/181). There have been comments about extending voting periods can cause decisions to take too long… but it takes longer to not reach quorum and throw the vote away. Adding extra time to vote _ **could** _ help solve this.
> - Voting Schedule: I like the idea of having it split in 2 in the weekend as it accommodates for individual contributors that might need some time in the weekend to review and cast their votes due to other comittments during the week.
> 
> > [@Optimizing Lido On-chain Voting Timelines for Inclusive Governance](https://research.lido.fi/t/optimizing-lido-on-chain-voting-timelines-for-inclusive-governance/8265/19):
> >
> > Voting Schedule: start voting on Wednesday at 14:00+ UTC, ending on Monday at 14:00+ UTC.
> 
> The fact that it’s not a lot of “office hours” for the objection phase should be monitored and potentially mitigated by big pushes to vote during the main phase - voting no, in the case of something that would have to be objected later.

# 5. [Update Lido on Ethereum Standard Node Operator Protocol - Validator Exits](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x969f9a3b3f52742b9763d8e128f2418a0ce888433e130a60f7fef809787ffdb4)

Forum post [here](https://research.lido.fi/t/update-proposal-lido-on-ethereum-standard-node-operator-protocol-validator-exits/8722/12)

### Vote: **For**

### Rationale:

Here’s the [full policy](https://lido.mypinata.cloud/ipfs/QmZTMfmJZsYHz61f2FjhYdh5VNu6ifjYQJzYUGkysHs8Uu), but I really like the side-by-side comparison found [here](https://github.com/lidofinance/documents-and-policies/compare/main...sssngth:documents-and-policies:9c6c2ff0c946a090282b5e1c2006d1c4302931f9#diff-8e84742a3e25074f049af8aa5a6c99b64562a9f6fae4f66871319ea36523041e).

The fact of the matter is the current policy does not take CSM nor SDVTM into account, and a new update is needed.

As a CSM NO myself AND a Lido Delegate, I feel these policies make sense and are written in a way that can be extended with future modules.

# 6. [On-chain vote #182](https://vote.lido.fi/vote/182)

### Vote: **Yes**

### Rationale:

This is a re-run of the previous vote that failed to reach quorum. My rationale is the same, quoted below:

> [@Lanski](#):
>
> On-chain votes reflect decisions already taken by vote. Some snapshot, some by the relevant committee.
> 
> 1. **Change Easy Track limits for PML and ATC** following the Snapshot decision. **Reduce the PML limit** from **6M** to **4M** , and **increase the ATC limit** from **1.5M** to **7M** in USDC/USDT/DAI per quarter to reflect operational changes.
> 2. **Increase the Lido Stonks stETH limit to 12,000 stETH and reset spent amount** , as per the Treasury Management Committee’s decision to achieve TMC-1. Resetting spent amount will allow swapping up to 12,000 stETH in 2024, and the limit will be reset again on January 1, 2025, as originally scheduled.
> 3. **Update the reward address** for Node Operator `ID 16` (Simply Staking), as requested on the forum.
> 
> I see no problems with these as they have been previously discussed, or the change on the Node Operator ID is standard procedure.

---

_[View the full topic](https://research.lido.fi/t/pol-lanski-delegate-thread/8155)._
