Pol Lanski Delegate Thread

[Lanski]

Establish the stVaults Committee

Forum post here

Vote: Support

Rationale:

Excited about moving the stVaults forward. The committee is a great bootstrapping mechanism for a new part of the protocol that might need adjusting and overseeing. I also trust the members of the committee, but if they took decisions that me or other governance participants disagreed on, a new vote can be put forth to change the committee’s role, its configuration or dissolve it entirely.

NEST - Network Economic Support Tokenomicsl

Forum post here

Vote: Approve

Rationale:

What are we doing here? Buying LDO back? Why is this a good thing? Let’s analyse this:

@steakhouse

order of stETH for LDO and routes it back to the Lido DAO treasury, effectively taking it out of circulation. The net effect it has is essentially to change the respective share over governance rights that holders enjoy, including over future ‘value distribution’ proposals.

It basically means that:

• Generates demand for LDO
• “change the respective share over governance rights” is a bit misleading or maybe I’m not understanding. It’s true that if someone sells, they will have less governance (duh), but it’s not clear not enforceable who will be selling and how this new configuration of the governance change and whether it will be positive. The only thing we know is that the treasury will have more LDO.

It also hints at “future ‘value distribution’ proposals”, which is nice because we regularly get proposals in the governance to “distribute value among tokenholders”, but aren’t quite completely thought out.

Lido V3 — Design & Implementation Proposal

Forum post here

Vote: Yes

Rationale:

I could not possibly explain it better than this:

@TheDZhon

Strategically, V3 delivers on GOOSE-2: Lido evolves from “the pool” to a platform others can build on, supporting a diverse product line. It aligns incentives: operators win direct demand; builders compose new products; stakers gain choice without losing liquidity. Vault isolation and opt-out mechanics mitigate the risk of DAO-imposed upgrades without a vault owner’s consent, ensuring vault sovereignty and an effective escape hatch.

To me, the key here is to keep the simplicity of the original Lido pool while at the same time providing flexibility to the operators and builders that would need more functionality, choice, and composability.

Vote 192

Vote: Yes

Rationale:

1. Upgrade to CSM v2 and increase CSM stake share limit from 3% to 5%, as per Snapshot decision. Items 1.34-1.59. Audit & deployment verification by: Statemind | Ackee.
2. Activate Triggerable Withdrawals, as per Snapshot decision. Items 1.1-1.33, 1.60-1.66, 2-4. Audit & deployment verification by Statemind | Audit by Ackee.
3. Update the reward address and name for Node Operator ID 25 Nethermind, as per Snapshot decision. Items 1.67, 1.68.
4. Rotate Deposit Security Committee address for Kiln. Requested on the forum. Items 1.69, 1.70.

All these issues have either been approved by snapshot vote before or are a consequence of the Kiln’s security issue.