Lido had two ways to buy back its token this fall.
One involved a committee deciding when to trade, how much to spend, and whether the market was safe enough to enter. The other was supposed to handle those decisions automatically, with a smart contract doing the accounting and permissionless execution replacing human discretion.
Guess which one was actually buying LDO.
On October 27, Lido’s Growth Committee reported that it had already converted more than a third of its latest 1,000-stETH allocation into LDO. The purchase belonged to a discretionary accumulation program that had spent months buying the governance token when its price looked attractive relative to Ether.
Meanwhile, NEST, the automated system Lido activated on August 10, had yet to purchase a single LDO as of the October 7 governance investigation.
Its accounting counter stood at negative $542,451 at the end of September.
The contrast was difficult to miss. Lido had built an automated buyback mechanism with a $10 million annual spending ceiling, but its human-run program was doing the purchasing while the automated one waited for better economics.
The odd part? NEST wasn’t broken.
It was following the rules.
And those rules reveal a surprisingly complicated question for a protocol that wants to connect its business performance with the value of its token.
What exactly counts as money available for a buyback?
The Buyback That Started Below Zero
Lido introduced NEST as a way to connect the success of its Ethereum staking business more directly to LDO.
Until then, LDO primarily represented governance rights. Lido could generate considerable staking revenue, but that didn’t automatically translate into a recurring mechanism for acquiring its governance token.
NEST was designed to change that.
According to Lido’s official buyback framework, the system monitors the DAO’s share of staking revenue and compares it with an annualized baseline of $40 million.
When revenue exceeds that baseline, NEST allocates half the surplus toward buying LDO, subject to a $50,000 daily cap and a $10 million rolling annual ceiling.
The mechanism executes purchases through CoW Swap when its conditions permit.
It sounds straightforward enough.
But there’s a feature that changes everything: NEST maintains a cumulative budget counter.
If eligible revenue falls below the threshold on a given day, the counter moves deeper into negative territory. Future revenue must first erase that accumulated deficit before the system can spend anything.
A profitable day, by NEST’s definition, doesn’t necessarily mean a buyback day.
In October, an independent researcher named Kuzmich decided to investigate why the mechanism had remained inactive.
He reconstructed the allocator’s logic from verified contracts, checked 32 on-chain budget recalculations, and rebuilt historical staking revenue using Ethereum events and Chainlink prices.
His October 7 findings revealed the $542,451 deficit.
There was also an unusual detail buried in its origins.
Roughly $147,658 of that shortfall accumulated during the four days between NEST’s activation and the connection of its revenue source.
The system began counting against its daily baseline before receiving the income data needed to offset it.
Lido later acknowledged that this followed from the technical limitations of the launch.
The remaining shortfall primarily reflected weaker-than-required staking revenue, with additional differences caused by the timing of revenue recognition.
None of this represented money Lido owed to a creditor. The negative balance was an internal spending allowance, not a financial liability.
But it created a real obstacle to purchases.
With the revenue structure modeled by Kuzmich, Ether needed to trade near $2,668 for NEST’s eligible staking revenue to cover its daily baseline.
Even moving slightly above that level wouldn’t immediately solve the problem. The system would first need to recover the deficit it had already accumulated.
Kuzmich calculated that at a constant ETH price of $2,700, the first purchase could remain 838 days away under his October assumptions.
That wasn’t a prediction of when NEST would actually buy. It was a fixed-price simulation, and changing revenue, ETH prices, or DAO parameters could dramatically shorten or lengthen the wait.
Still, a mechanism intended to make tokenholder value accrual more systematic had run into a peculiar situation.
It could be ready to execute a transaction and still have no authority to spend.
And the deeper we look into Lido’s finances, the more interesting that restriction becomes.
A Profitable DAO Can Still Fail NEST’s Test
Lido’s H1 2026 financial report provides the first important clue.
During the first six months of the year, the DAO recorded $15.94 million in total net revenue against $14.33 million in Foundations’ expenses.
That produced a $1.61 million operating surplus before non-recurring items.
Not spectacular, but positive.
Then came a $6.06 million one-off expense related to the Kelp incident, leaving the DAO with a total reported loss of $4.45 million for the period.
Those figures show why defining surplus is harder than it sounds.
Depending on which costs belong in the calculation, Lido could report an operating surplus and an overall loss for the same six months.
NEST doesn’t reconcile those results.
It monitors eligible staking revenue, not the DAO’s complete income statement.
Ravel calculated another useful comparison from the report.
Lido generated $15.71 million in net staking revenue during the first 181 days of 2026. Annualizing that result produces a run rate of roughly $31.68 million.
That’s $8.32 million, or 20.8%, below NEST’s $40 million annual baseline.
The comparison isn’t exact. Financial-reporting revenue and the specific on-chain revenue recognized by NEST differ in scope and timing. The first-half run rate also doesn’t establish what Lido would earn later in the year.
But it helps explain why the automated system struggled to find a surplus.
Its threshold sat well above the pace of staking income visible in the first-half accounts.
And that raises a question the NEST contract cannot answer by itself.
What if Lido becomes more profitable by spending less?
Consider two simplified hypothetical years.
In the first, Lido earns $38 million in qualifying annual revenue and spends $30 million.
The business produces an $8 million operating surplus.
Yet NEST’s $40 million threshold would still reject that revenue as insufficient. Assuming it arrived evenly throughout the year, the counter would accumulate another $1 million deficit after applying the 50% sharing rule.
Now reverse the situation.
Suppose qualifying revenue reaches $42 million, but operating expenses total $43.8 million.
The business loses $1.8 million.
NEST, however, recognizes $2 million of revenue above its threshold and adds $1 million to its buyback allowance.
If the counter began at zero and sufficient funds were available, that allowance could support purchases despite the operating loss.
These are Ravel’s illustrative calculations, not Lido’s actual financial results. They assume qualifying revenue represents total operating revenue, ignore other income and exceptional costs, and isolate the effect of the threshold. An existing negative balance would still need to be cleared before purchases could begin.
The examples expose the fundamental limitation.
NEST measures revenue above a fixed hurdle. It does not measure profit after actual expenses.
That’s not necessarily a mistake. The design deliberately avoids relying on financial reports that arrive later and may require judgment about how to classify spending.
But it means the mechanism can produce outcomes that don’t line up neatly with the DAO’s broader economic performance.
And there’s another complication.
The $40 million threshold wasn’t even identical to the spending plan Lido had approved.
The $3.8 Million Gap Nobody Can Buy Back
When Lido submitted its 2026 Ecosystem Grant proposal, the Foundations requested $43.8 million in baseline funding.
Another $16.2 million was available under a discretionary spending cap, bringing the maximum request to $60 million.
That baseline included protocol maintenance, security, engineering, growth initiatives, and the development of new revenue streams.
NEST, meanwhile, used its separate $40 million revenue threshold.
The difference was $3.8 million.
In other words, the automated buyback’s income hurdle sat 8.7% below the baseline spending request.
Lido subsequently reported a lower projected full-year foundations expense figure of $37.7 million, while its H1 financial report also referred to a $41 million baseline grant request. Those figures describe different budget and reporting references, rather than proving that any single number equals actual annual expenses.
But that’s precisely the problem Kuzmich wanted governance to address.
A fixed threshold doesn’t automatically respond when the DAO approves a smaller budget or discovers it can operate more efficiently.
If management cuts spending without changing the NEST threshold, the system won’t recognize those savings as additional capacity to buy LDO.
Kuzmich proposed tying the threshold to the annually approved Foundations budget.
His updated simulation explored 1,000 possible ETH price paths over the 12 months beginning October 1.
Under the existing configuration, with a $40 million threshold and modeled expenses of $43.8 million, the median annual buyback was zero. Only 47% of simulated paths produced at least one purchase.
When both expenses and the threshold fell to $35 million, the median buyback increased to $1.26 million, and the proportion of paths with purchases rose to 69%.
At $30 million, the median reached $3.18 million, with purchases occurring in 89% of scenarios.
Those aren’t promised outcomes. They’re model results that depend on future ETH prices, expense assumptions, and how revenue develops.
And cutting $13.8 million from a budget is considerably harder than changing a smart contract parameter.
Someone has to decide which projects stop receiving funding.
That is where the economic question becomes a governance problem.
Lido contributor Jenya_K agreed that linking the threshold to the approved budget deserved consideration in the 2027 grant request.
But he pushed back against treating $30 million as a predetermined target. Any reduction, he argued, needed to come from detailed operational planning rather than a model optimized to produce more buybacks.
There is a good reason for that caution.
Lido isn’t simply maintaining an Ethereum staking contract. It funds security work, infrastructure upgrades, institutional expansion, and products intended to diversify revenue beyond staking.
Cutting those investments could improve short-term buyback capacity while damaging the business expected to fund future purchases.
The research also found another uncomfortable outcome.
In Kuzmich’s revised model, 26% of the buyback volume under the current setup occurred in loss-making years when treasury income was excluded from the profit calculation.
Aligning spending and the threshold at $30 million reduced that figure to 13%.
That doesn’t mean the existing contract has already spent treasury funds recklessly. It means its design doesn’t guarantee that every future purchase will come from actual accounting profit.
The distinction is the entire point of the investigation.
NEST protects the DAO from spending too quickly according to a specific revenue test.
It doesn’t know everything the DAO earns, everything it spends, or whether the resulting business is profitable.
Meanwhile, the Humans Were Buying
While NEST waited for the right conditions, Lido’s separate accumulation program kept operating.
The DAO approved that program in April to acquire LDO using treasury-held stETH when the token appeared inexpensive relative to ETH.
Unlike NEST, the program doesn’t depend on a recurring revenue-surplus calculation.
Its Growth Committee operates within approved limits, using price caps, execution windows, and batches that tokenholders can challenge through governance.
By August 25, Lido had reported acquiring about 14.8 million LDO using 2,320 stETH.
A subsequent September 25 execution report documented another 4.58 million LDO acquired using 680 stETH.
Together, those reported purchases exceeded 19 million LDO.
And on October 27, the committee said it had already converted more than one-third of the fourth 1,000-stETH batch.
The humans were making trades while the autonomous mechanism waited.
Then the market delivered a reminder of why discretionary execution exists.
Following the October 29 Binance security incident, Lido temporarily paused its manual accumulation program.
In a November 4 governance update, Lido said 6.24 million LDO had left a Binance hot wallet during the attack and that the receiving address subsequently sold the tokens through Uniswap V3.
Lido reported no loss of DAO funds.
The Growth Committee reviewed counterparty exposure and resumed purchases once it considered operations safe.
The incident did not establish a problem with NEST’s smart contracts. It affected the separate discretionary program.
Still, it created a revealing contrast.
The automated mechanism was designed to remove day-to-day human discretion from buyback decisions.
The manual program retained that discretion, including the ability to pause during an external security shock and resume when conditions improved.
Neither approach is inherently superior.
Automation offers predictable rules, limits discretionary intervention, and allows outside participants to verify how the mechanism operates.
Human oversight can respond to circumstances that a narrow revenue formula doesn’t capture.
Lido has chosen to operate both.
But the existence of a manual program buying millions of tokens raises an awkward question about what the automated one is ultimately supposed to accomplish.
It gets more complicated when the purchased tokens reach the treasury.
Buying LDO Isn’t the Same as Burning It
NEST launched in Treasury mode.
Under that configuration, purchased LDO returns to the DAO treasury rather than undergoing an automatic token burn.
The accumulation program also returns its purchases to the treasury.
That can reduce tokens available to the broader market while the DAO continues holding them, but it does not permanently reduce LDO’s total supply.
The DAO retains control over what happens next, subject to its governance procedures.
Some community members have argued that NEST should permanently burn the tokens it acquires, creating an irreversible reduction in supply.
Kuzmich has expressed support for that direction.
But a burn is not currently the default destination of NEST purchases, and introducing one would require governance action.
This distinction matters because crypto buybacks can serve different economic purposes.
A DAO might acquire its token to hold treasury reserves, provide liquidity, fund future programs, or remove tokens permanently.
All involve purchasing the asset.
They don’t necessarily produce the same result for existing holders.
In NEST’s case, the immediate mechanism is treasury accumulation, not an automatic reduction in total token supply.
That doesn’t make it meaningless.
It simply means the promised connection between protocol success and tokenholder economics remains more indirect than a conventional buyback-and-burn headline might suggest.
And it brings us back to the question Lido’s governance community must answer.
What does success look like?
More purchases? Fewer tokens in circulation? Sustainable profitability? A stronger treasury? A growing staking business?
Those objectives can overlap.
They can also compete for the same dollars.
The Buyback Is Working as Designed. That’s the Debate
NEST’s supporters have a serious argument in their favor.
A DAO that mechanically spends a fixed percentage of revenue can end up buying its own token while its operating losses deepen.
Kuzmich’s own stress testing illustrates the danger. A hypothetical policy allocating 10% of net staking revenue directly to buybacks would purchase more consistently, but its model placed 56% of the resulting buyback volume in loss-making years.
The current mechanism is deliberately more restrained.
Its cumulative deficit prevents one strong revenue day from immediately erasing months of weak performance. Its daily spending cap limits exposure, and its governance architecture keeps parameter changes under DAO control.
Those protections have value.
Lido contributors also argue that some income sources remain too small or operationally different to justify immediate integration into NEST. The system was built to accommodate additional revenue sources later.
None of that eliminates the accounting question.
A mechanism designed around a fixed revenue threshold cannot independently determine how much profit the DAO actually generated.
And if the threshold isn’t connected to spending, improving operational efficiency doesn’t necessarily increase buybacks.
Lido’s next opportunity to address that mismatch may come with its 2027 budget process. On October 22, a contributor indicated that the grant request was expected toward the end of November.
That could allow governance to consider the revenue threshold and spending plan together.
It could also leave the current arrangement intact.
The available evidence doesn’t establish that NEST has failed technically or that its conservative parameters are financially irrational. The last documented zero-purchase finding reviewed for this investigation dates to October, and Ravel has not independently verified the executor’s complete transaction history through November 4.
What the evidence does establish is a structural gap between the revenue NEST measures and the wider financial results Lido reports.
For a protocol trying to connect economic success with tokenholder value, that’s not a minor accounting detail.
It’s the question at the center of the entire promise.
Lido built a system that knows when staking revenue clears a predefined hurdle.
It built controls to prevent purchases when that hurdle isn’t met.
It even gave governance the authority to change the rules.
But the hardest part was never teaching a smart contract how to buy LDO.
It was deciding what Lido could afford to spend in the first place.
