A message to the Lido team

First of all, let me state that this post is not intended to insult or belittle anyone’s achievements.

However, it is time to engage in an open dialogue with users and token holders.

As a crypto project, Lido is actively losing ground to the market and other teams.

When the team is asked uncomfortable questions, they block accounts to silence users. Is this how a DAO or DeFi project should behave?

A post regarding this was created on X

Aksusarya on X: "Let’s talk about @LidoFinance $LDO 1. They position themselves as a "top-tier staking" project—boasting the largest amount of staked $ETH and a long-standing, proven track record. However, let’s look at it from the perspective of an active crypto community member and examine the… / X (I will repost it in the comments).

Yet, the team decided they were above it and ignored that as well.

It is time to enter into an open dialogue with LDO holders and answer questions honestly; losing the project’s footing in a rising market is unthinkable.

So, I ask the following:

  1. The team should come to this post and answer questions.

  2. Provide a full report on projected expenses for 2025–2026.

  3. Conduct an independent audit of operational expenses and salaries.

  4. Drastically cut the budget and redirect funds to support LDO.

  5. @lidoecosystem-ops also ask to provide a detailed explanation as to why user inquiries were ignored (see screenshots).

I ask that you not ban my account again, but instead engage in an open dialogue.

The project is losing its reputation by the day, while other projects are developing and introducing innovations. Old does not mean good.

2 Likes

Let’s talk about @LidoFinanceLidoFinanceLidoFinanceLidoFinance $LDO

1. They position themselves as a “top-tier staking” project—boasting the largest amount of staked $ETH and a long-standing, proven track record.

However, let’s look at it from the perspective of an active crypto community member and examine the problems it faces.

In five years, the project has failed to generate stable revenue; the team spends $40 million annually on itself (operating expenses).

No one understands where such colossal sums are actually going.

2. Governance.

The team completely ignores questions from the community unless they come from developers or delegates close to the project.

As for the delegates, they vote on or discuss *only* those ideas that originate from the project team itself.

Batching, delays, low rates to reduce buybacks — these are all ways to minimize returns to holders. But projects they favor get funded fast. Governance is more form than substance, ultimately serving the vested interests of a few

3. Buybacks.

On the forum (research.lido.fi), you can find numerous threads and proposals regarding buybacks that the team has ignored for years. These topics simply get lost in the forum, and no one ever revisits them.

When $LDO began to look like useless junk, the NEST program was launched after six months of discussion.

Two months after the launch, exactly $0 worth of buybacks had been executed through it.

You might ask why. It’s because the team set a condition that buybacks would only begin once $ETH reached $2,730—a price point we might not see for years—meaning there will be no buybacks until then.

stETH/LDO Buybacks.

A budget of 10,000 stETH was allocated for buybacks, intended to be distributed in monthly tranches of 1,000 stETH.

The initial price was set at 0.000163 $LDO/$ETH.

After five months, only 2,300 out of the 10,000 have been executed.

Why? …because the team is waiting for the price to drop to that level, fearing they might overpay—even though $LDO already looks dead.

And every month, the team simply lowered the price threshold. Right now, it stands at 0.000153 $LDO/$ETH.

When the issue of raising the threshold to 0.0002 was raised on the forum—and despite three objections against continuing buybacks at current levels—the team simply ignored it (see screenshots).

4. Loss of market share

We can@ether_fial@ether_fi see what @ether_fi ($ETHFI) is rolling out.

Why ETHFI tvl 6b and mcap 600m?

And LDO tvl 24b and mcap 350m?

So,what coin is useless ?

We can all see how $Eigen is growing.

Why don’t we see the same with $LDO?

Because the team is completely stuck in the past and refuses to change anything.

Lido labs needs to cut half the team and make

the programmatic buybacks much more

aggressive on every parameter

This team is burning, an absurd amount of

money relative to their accomplishments and

growth

The token needs to be treat as casino

@LidoFinance team has no sympathy for the $ldo token holders.

They don’t care about the community’s ideas at all.

They have always looked down on the LDO holders

with arrogance. They have always wanted to

monopolize all the benefits of the protocol.

Why does the project prioritize stakers while LDO holders incur losses?

Don’t you think that $10 million in annual buybacks against a FDV of $300 million is a paltry amount?

Can the Lido team provide reports on how the $40 million annual budget for operating expenses and salaries is spent?

Why do some projects carry out buybacks without any triggers, while Lido—with billions in TVL—imposes conditions just to delay the start of buybacks?

@vsh @Izzy @KimonSh @dgusakov

@polar @cp0x @Ginsing @JackLido

@Leuts @Nansen @BCV @Lanski

Thanks for taking the time to write this up. But for me, as a contributor, it felt like you were ignoring some important parts and, at the same time, interchanging ideas one with another.

A few points I want to cover and highlight as an individual contributor, not as the Foundations representative:

On moderation.
No account has been removed for criticizing Lido Foundations. What was actioned matches the forum’s rules on coordinated activity: a cluster of accounts created within the last few days, posting near-identical content, with no prior activity on this forum. That is a very different from silencing LDO holders. Anyone in that group who is a real LDO holder is welcome to post under their own account and engage, this one hasn’t been touched.

On the cost of this. Time contributors spend responding to coordinated posting waves is time taken away from the work as reporting, infrastructure, product.

On the $40M and “no one knows where it goes.”
This is published. The H1 2026 report (Lido DAO GOOSE-2026 Report H1 2026) covers the Foundations’ expenses line by line. If, after reading those, specific line items look unjustified to you, that’s a concrete conversation worth having.

On the NEST execution.
Exact threshold logic was discussed during the voting cycles, and any holders had the possibility to vote to say for and against, and that was only silence.

On “the protocol prioritizes stakers while LDO holders lose.”
Stakers aren’t prioritized over holders, they’re the source of the revenue that any value to holders comes from. Protocol fees fund the DAO treasury. A protocol that lost its stakers would have nothing to return to holders at all. The two aren’t in competition; one funds the other.

On changing the parameters.
If you hold LDO and believe the buyback thresholds are too conservative or the expense base too large, the mechanism to change that exists and is open to you: a proposal and a vote.
Every one of these parameters was set by governance votes, votes where an “against” option exists and is counted. Those votes show no meaningful opposition. If the concerns in this thread were widely shared among holders, that’s where it would be visible.

3 Likes

Hello. I don’t think the DAO has any problem with operating expenses. I only have some personal thoughts on the buyback. The essence of a buyback is to strengthen mutual trust between holders and the DAO. If the DAO’s buyback looks bearish or keeps getting smaller or lower, then the buyback is actually failing. Reducing supply and strengthening the treasury is the plan, but it should also strengthen holder confidence. I agree that spending during an expansion phase is meant to bring greater returns. However, I believe the buyback could clearly be done better. Right now it signals that the LDO/ETH rate will keep declining, and the more thresholds are set, the more holder expectations are worn down.

A manual buyback is a product of subjective judgment. I think it should be changed to an automatic buyback. For example, set an LDO/ETH exchange-rate ceiling of, say, 0.0005, and buy back automatically every week. That way, the operator won’t be put in a dilemma. Split the remaining stETH across 36 weeks and automatically use 200 stETH per week to buy back LDO, giving the market a fair competitive environment. This gives us enough time for holders to understand what the DAO is doing, while strengthening holder confidence and avoiding subjective judgment. Whether LDO is undervalued or overvalued at any point, our machine keeps running automatically and lets the market decide. We should not signal that we are willing to exchange at a better rate to acquire LDO, because that itself is a view on the market and already affects market expectations. Just my personal thoughts. Thank you.

Then Nest’s buyback mechanism really does have some design issues. The DAO’s revenue is publicly verifiable, and people who are willing to hold LDO long term obviously want to be tied to LDO’s future growth. They want to bet on LDO achieving something greater in the future, not on a ceiling they can see at a glance. Take Uni’s burn mechanism: no one can calculate its ceiling; it grows along with the industry. Designing a hard cap of 10 million is quite unreasonable. It will disappoint all LDO holders. Holders may not be afraid of short-term setbacks, but they are afraid of a protocol whose future is so visibly limited.

I think it could be revised to: above 40 million, 10 million used for buybacks, and then 50% of the remaining revenue used for buybacks while 50% flows back to the treasury. Only in this way will people be willing to believe that LDO’s growth is connected to its holders.

1 Like

Thanks for answers

Regarding the $40M and the H1 2026 report—having high-level line items is not the same thing as actual financial transparency. Saying “it’s all published” misses the point of why holders are frustrated.

First, these reports only show broad, aggregated categories. We see millions allocated to “Foundations’ Expenses,” but token holders have zero visibility into the actual breakdown—individual contributor milestones, leadership KPIs, or where that capital is exactly deployed.

Second, the report itself highlights a massive disconnect between spending and performance. For example, why is the DAO funding non-core initiatives like Wisp (a consumer AI subscription tool)? It has zero synergy with liquid staking, brings no protocol revenue, and looks like clear scope creep while the treasury is being drained.

At the same time, the protocol’s daily revenue dropped from ~$153k last August to around $69k this June. If we are structurally loss-making at current ETH prices, and 2 out of 4 major GOOSE-2026 strategic goals are explicitly marked as “off track” (like stVaults), we can’t just wave away concerns by saying the expenses are justified just because they’re written down on a line item.

True accountability isn’t just proving that the money was spent; it’s proving that it was spent efficiently to drive actual value back to the protocol and LDO holders. Right now, the math just doesn’t add up.

Let’s be precise about the timeline and market conditions for NEST. Saying “holders voted for this, so it’s on them” is a major distortion of what actually happened.

When the NEST parameters were being finalized and voted on between May and August 2026, the revenue decline was already fully visible. The team ran backtests using outdated 2024–2025 data to justify the $40M baseline. But by the time NEST actually went live on mainnet on August 14, 2026, everyone knew the protocol’s daily revenue was already sitting around $69k—far below the $109k/day ($40M annualized) trigger.

The core team designed a mechanism that was mathematically guaranteed to be dormant from day one, given the economic reality at launch. Token holders didn’t “silently agree because they liked the parameters”—they were simply presented with a binary choice: take this overly restrictive, non-functioning band-aid or get nothing at all.

Pointing to governance votes to defend a system that hasn’t executed a single buyback since launch because its thresholds were intentionally disconnected from current revenues is just deflecting. The design was flawed at deployment, and pretending it’s a community-driven choice doesn’t change that.


For me personally—as well as for everyone who saw this—it looks exactly like prioritizing stakers.

Telling frustrated holders to “just go write a new proposal and vote” feels like pure deflection. As I already pointed out in my previous posts, delegates largely ignore requests from regular users anyway.Core contributors and the foundation receive millions of dollars in funding specifically to design, monitor, and optimize the protocol’s economic architecture. That is their job. Expecting individual, retail token holders to act as full-time financial engineers and fight against delegate inertia just to fix a flawed parameter layout is completely unrealistic

Since all the buyout offers were published by @lidoecosystem-ops and @steakhouse I suggest inviting them to the conversation.

*(Note: English is not my native language, so I am using AI to translate and articulate my thoughts clearly here.These posts are not AI-generated; they are simply structured. Thank you for understanding.)

2 Likes

A user on X suggested asking for advice from @Hasu
So, I’d like to hear your opinion, please.

@dgusakov Following your advice, I am submitting this for discussion and a vote. Let’s see how “your” delegates vote on a proposal that did not originate from the team.

I also look forward to hearing your opinion on this matter.

Thank you for your attention.

The contributor class’s income is decoupled from LDO’s price. Their salaries are mostly denominated in stablecoins, and budgets are drafted with their own participation and approved through a governance process they themselves control. This creates a closed loop: the people who write the budgets, approve the budgets, and receive the budgets are the same group — while the token holders who generate the system’s revenue are not in that loop. This isn’t theft. It’s “legally taking care of themselves first.”

  1. The four gates in the NEST they designed are a product of this closed loop. Go back to the design: every gate is there to prevent “too much money from flowing out,” and not one is there to prevent “too little money from flowing out.” If the designers’ goal were to benefit token holders, you would see holder-protecting clauses like “a mandatory minimum buyback when revenue falls below X” — there isn’t a single one. But budget-protecting clauses (daily cap, annual cap) are all present. The design gives away where they stand.
1 Like

As u can see ,team and delegates completely ignores my messages, while LDO is dying)

Great! Once you feel that enough discussion time has passed (usually it is 1-2 weeks), feel free to proceed with the snapshot proposal here - Snapshot (create new proposal). Note that you need to have at least 1000 LDO to be able to submit a proposal.

2 Likes

With the team’s involvement, I’ve already seen some positive feedback.

What team involvement?

U see any proposal from them or something else?

The team has already provided a clear path for how user feedback could be implemented, and they are encouraging users to participate in the discussion and help develop more detailed proposals for the changes. In my view, this already represents a positive response.

What should be done now is to spread the word as much as possible, so that more people become aware of this, join the discussion, and contribute to developing a more comprehensive proposal. This process itself can also help move Lido forward in a positive direction. At the very least, it shows that the team is listening to user feedback and is willing to try to make changes. That is still something worth respecting.

Whether the final proposal passes through a vote depends on the choice of $LDO holders. The team cannot directly determine the outcome.

Simply insulting or attacking the project will not help move anything forward. In fact, it could have the opposite effect by causing more external users to distance themselves from the project. Choosing an appropriate way to address problems is what really matters.

From my perspective, the team is making some changes and showing a willingness to listen to users and make adjustments. So, rather than continuing to attack the project, I think it would be more constructive to stop the hostility and communicate about the project in a more objective and positive way. Helping more external users develop a positive and accurate understanding of Lido would be a more rational approach.

There is also something worth mentioning about the Lido team building usewisp_io. I don’t think there is anything inherently wrong with it. If a project wants to develop additional sources of revenue, it needs to explore different directions. No team can guarantee that every product it creates will immediately become profitable.

Moreover, I believe usewisp_io is a good product. The constant criticism and attacks against Lido within the community are creating an environment that makes it difficult for external users to form an accurate understanding of the products created by the Lido team.

When a project is surrounded by constant hostility and negativity, many external users may simply choose not to learn more about the products being built, because they may come away with the impression that the team itself is unreliable.

usewisp_io is somewhat like a privacy-focused version of Lobster, and I think that is a very interesting direction.

What Lido needs is to properly manage its relationship with the community and respond constructively to user feedback. The two sides should work together rather than treating each other as opponents. If that relationship can be improved, community members could also become a powerful force in promoting usewisp_io to the outside world.

2 Likes

If I’m not mistaken, these are your posts.

There’s a hint of hypocrisy in your messages.