Pol Lanski Delegate Thread

[Lanski]

This time I’m going to bundle the rationale for 3 out of the 4 proposals because they are heavily intertwined:

1. GOOSE 2025 cycle: Lido DAO goals for 2026

Forum post here

Vote: Adopt GOOSE-3 proposal

2. Ecosystem Grant gRequest (EGG): Executing GOOSE-3

Forum post here

Vote: Approve 2026 EGG

3. Lido Alliance BORG – Amendment of Bylaws to Enable GOOSE-3 Execution

Forum post here

Vote: For

Rationale:

This sets the strategy for 2026. And in terms of strategy, too many cooks spoil the broth! I think the GOOSE-3 is a solid exercise, although I had some comments to offer.

These comments can be found here:

[Lido Labs] GOOSE-3: Lido’s Next Chapter

First of all, thanks for putting this proposal together. Topic of the year: How do we navigate the tension between maintaining the current setup, continue making it safe and helping Ethereum (which have been largely achieved, but need to be upheld or we lose all competitive advantage) and finding new exciting avenues for revenue and relevance. We get it, infra is boring and It’s cool to do hot shit in DeFi, but DeFi at large is a huge animal that needs to be scoped better. Going step by step: …

The TL;DR is

@Lanski

Overall, I would encourage to lean ETP/Fs, think careful about the Node Operator set and how to keep it decentralized, be careful on spending resources wildly on DeFi but experimenting, (maybe externalizing?) and waiting until that opportunity to replicate success in the proven Lido formula.

I also recommend reading @KimonSh 's thoughtful response to my comments, particularly in regards to Node Operator set decentralization and his optimistic view on what stVaults bring to the table.

I LOVE that Lido’s main problem is that it’s too stable and safe. This is the purpose of a DAO-led infrastructure project. If the whole team were to disappear, we (LDO holders) could upgrade the contracts in maintenance mode and it would keep going forever with the necessary tweaks around protocol upgrades.

That said, I’m also in for exploring how to leverage this stable base we have to grow and make the most decentralized staking protocol the base for decentralized finance too.

Adopt The SEAL Safe Harbor Agreement

Forum post here

Vote: Approve

Rationale:

No matter how many audits, how many eyes are in a project, the fact that the backend (the smart contracts) of blockchain projects is exposed for anyone to validate and trust, it also means that bad actors can be permanently scanning, testing, probing and finding ways to exploit such smart contracts.
In our industry, white hats have a history of having rescued millions and millions from the hands of hackers. They put their skills at work either proactively or as an incident response team to help users and ultimately the reputation of our industry, and sometimes they have to get dirty and do the same things the hackers do.
The Safe Harbor Agreement recognises them, their importance in our industry, and welcomes them in advance, offering safe harbor within a framework published by SEAL, a good representative of such white hat hacker groups.
While I hope there are no incidents ever, I’m happy to know that if white hackers jump in to protect Lido, they are also protected by this agreement.