Aragon #199
Vote: FOR
Rationale:
Verification guidelines: Notion
A lot of housekeeping:
- Deactivate Node Operator A41, as requested on the forum.
- Change name and reward address for Node Operator Stakin, as per Snapshot decision. Items 1.2, 1.3.
- Upgrade Lazy Oracle, as proposed on the forum. Audit & deployment verification: MixBytes. Item 1.4.
- Rotate address for Oracle Set member Chorus One, as requested on the forum. Items 1.8–1.13.
- Rotate address for Oracle Set member Stakefish, as requested on the forum. Items 1.14–1.19.
- Set Node Operator Chorus One soft target validators limit to 0, as requested on the forum. Item 1.20.
- Decrease Gas Supply Easy Track limit from 1000 to 150 stETH per year and reset spent amount for the 2026 period, as proposed on the forum. Items 1.21, 1.22.
- Rotate Deposit Security Committee address for Stakefish, as requested on the forum. Items 1.24, 1.25.
- Upgrade stVaults Easy Track factories to register groups and register & alter tiers in Operator Grid, as proposed on the forum. Audit & deployment verification: MixBytes. Items 6-11.
I’m excited about raising the stake share of CSM!
- Raise Community Staking Module stake share limit to 8.5% and priority exit threshold to 10.2%, as per Snapshot decision. Details in the forum post. Item 1.23.
Security-related - all audited.
- Upgrade Curated and SDVT Staking Modules Easy Track factories for validator exit request hashes submission, as proposed on the forum. Audit & deployment verification: MixBytes. Items 2-5.
- Upgrade and re-enable ZKSync Bridge, as proposed on the forum. Audit & deployment verification: Cantina. Items 1.6, 1.7.
- Upgrade Vault Hub, as proposed on the forum. Audit & deployment verification: MixBytes. Item 1.5.
From LNOSG to CMC: Evolving Curated Staking Modules Governance
Forum post here
Vote: FOR
Rationale:
LNSOG walked so CMC could run. With CMv2, the Curator Management Committee (CMC) will manage operational workflows for CMv1, CMv2 and Simple DVT.
Introduce an Identified DVT Cluster type in the Community Staking Module
Forum post here
Vote: FOR
Rationale:
CSM being permissionless, anyone can use the setup they want - including DVT for resilience. That said, the economic incentives are not quite there to do so, because DVT introduces complexity and more machines and/or operators. Hence, it makes sense to me to introduce an Identified DVT Cluster (IDVTC) type in the CSM to incentivize these types of operators, which are desirable because of their resilience.
Increase Lido Alliance BORG Operational Easy Track Limits to align with EGG
Forum post here
Vote: FOR
Rationale:
Layering DAOs with operation companies isn’t straightforward, but suffice to say there’s no extra spending being approved here, just operations consolidation.
Authorize LDO Accumulation Program for up to 10,000 stETH
Forum post here
Vote: FOR
Rationale:
Token buybacks don’t work long term. I support this because I understand the pressure that LDO is facing in the face of the disproportionate drop of price in regards to ETH (a bear-er reaction than the bear market). Party, I talked about my position here: Liquid Buybacks: NEST execution with LDO/wstETH liquidity - #88 by Lanski
This proposal finds a good enough middle ground.
Redirect DVT & APM Incentives to Current Meta Treasury and LoL
Forum post here
Vote: FOR
Rationale:
Mellow incentives → Lido Earn
APM → LoL
Adapting incentive flows to where they can be more impactful. Yes please.
Lido DAO Ops Multisigs Policy 3.0
Forum post here
Vote: FOR
Rationale:
Periodic policy refreshes for DAO ops multisigs are healthy governance hygiene.