The Lido DAO is debating whether to link its 2027 grant budget to automated LDO governance token buybacks executed by its NEST engine. As of Oct. 13, NEST had recorded zero purchases funded by its allocator, with its running spending counter standing at minus $564,230.96.
Key Takeaways:
- Buyback Baseline: The NEST contract tracks daily staking revenue against a $109,589 baseline (approximately $40 million annually), feeding half of the difference into a running counter.
- Allocator Capital: The engine held 41.12 stETH on Oct. 13, following a single 41 stETH transfer on Aug. 28 and zero outgoing transactions.
- Financial Position: First-half accounts revealed $15.7 million in net staking revenue and $230,000 in Earn income, but a $6 million Kelp-related expense dragged net results to a $4.4 million loss.
- Model Corrections: Community member Kuzmich identified financial modeling mismatches showing NEST could execute buybacks even while the protocol operates at an overall loss.
Governance Debate and NEST Mechanics
The governance debate opened on Oct. 7 when contributor Kuzmich proposed tying NEST's revenue threshold to approved spending. In an Oct. 9 response, Jenya_K supported discussing the concept within the 2027 grant process but insisted figures must originate from bottom-up planning.
Under the active specification, NEST applies strict execution parameters: a $50,000 daily purchase limit, a $10 million cap per 365-day window, and a $1,000 minimum allocation threshold. While separate discretionary stETH-to-LDO purchases exist outside this framework, NEST does not currently capture monthly Community Staking Module (CSM) rebates or Earn income. Jenya_K noted that CSM rebates are already counted in financial reporting, meaning secondary inclusion would cause double-counting. Similar to broader sector reporting like Sky disclosing $4.4B PSM liquidity, accounting clarity is vital for protocol sustainability.
Financial Modeling and Expense Mismatches
Lido's first-half financial report outlined $15.9 million in net DAO revenue offset by $14.3 million in Foundations expenses, generating an operating surplus of $1.6 million. However, the $6 million Kelp-related one-off created an overall $4.4 million loss. Treasury bridge items included $1.4 million in treasury income and a $60.9 million asset-price effect outside profit-and-loss metrics. Meanwhile, the 2026 grant request listed a $43.8 million baseline, while full-year expenses were projected at $37.7 million.
On Oct. 11, Kuzmich updated a simulation model testing 1,000 ETH price paths starting at $2,679.84 with 61% annual volatility. The model demonstrated that setting an annual spending threshold at $40 million yielded mean modeled purchases of $2.32 million (median $0) and a mean pre-purchase loss of $1.92 million. At a $35 million threshold, mean purchases reached $3.35 million (median $1.26 million) with mean profit of $3.08 million. A $30 million threshold generated $4.71 million in mean purchases (median $3.18 million) and $8.08 million in profit.
Crucially, Kuzmich uncovered an expense mismatch: the code scaled a forecast expense curve ($39.8 million before scaling) down to $27.3 million for the $30 million budget row. When actual expenses equal the threshold, mean modeled profit at $30 million drops from $10.7 million to $8 million, raising the proportion of purchase-active paths ending in a loss from 12.6% to 22.2%. Furthermore, recalculating reset rules (after fixing a Sept. 2028 period overlap) showed average spending of $2.6 million per 365-day period with carry-forward versus $2.8 million under an annual reset. Risk management parallels can be drawn to protocol reserves such as Ethena's $4.76B USDe backing allocations.
Why It Matters
This governance debate underscores the technical and financial complexity of automating DAO token buybacks based solely on top-line revenue metrics. If smart contracts trigger buybacks without accounting for bottom-up operating expenses or one-off liabilities, a protocol risks draining capital while technically running at a net loss. Moving forward, Lido DAO members must decide whether true operational cost reductions or contract parameter adjustments will dictate LDO value accrual.
