Lido Audit Proposer Offers Two Budget-Transparency Paths After Deferring Vote

A revised community initiative puts external review and internal reporting reforms on the table ahead of Lido’s 2027 grant planning. Neither option is an approved DAO spending decision.

Published 7 November 2026. Development dates: 5–6 November 2026.

A postponed vote and competing revisions

Community proposer Cryp1 said on 5 November that a planned Snapshot vote was being held back for revisions. On 6 November, the proposer posted two alternatives in the financial-audit discussion.

The first narrows an external review to research-and-development spending and product efficiency, targeting $80,000 with a $150,000 ceiling. The alternative avoids external contractors, proposing internal reporting reforms, a 10–15% operational-budget reduction and 30–50% initial cuts for sub-products. These are the author’s requested changes, not commitments by Lido Labs or the Finance Workgroup.

The revisions follow objections from delegates including cp0x and Lanski to the original cost and scope. NetNapz has not verified an approved vote, procurement mandate, auditor appointment or treasury disbursement. Proposed reductions should not be reported as enacted cuts.

What the existing financial disclosure actually says

Lido’s H1 2026 report provides an important qualification to the debate. For January–June, it reports $15.9 million in net DAO revenue and $14.3 million in Foundations’ expenses: a positive $1.6 million operating result before non-recurring items. A Kelp-related one-off expense turned the total result into a roughly $4.5 million loss. The report is expressly unaudited and not prepared under a major GAAP framework.

It also explains that a revised product-based cost presentation prevents direct reconciliation with individual EGG budget lines. That is an accounting-presentation explanation, not proof of misconduct. Spending comparisons require consistent definitions and periods.

The same disclosure projected approximately $37.7 million of full-year Foundations’ spending, below its $41 million baseline request. Those are historical report estimates, not November-verified spending totals. Its H1 operating surplus and overall loss must be distinguished; neither alone describes the entire financial position.

Why the distinction matters for LDO governance

Lido’s governance documentation identifies LDO as the token used to vote on DAO decisions, including development spending and protocol parameters. A forum author can request reforms without binding the treasury or the teams named in a draft.

NetNapz assessment: the useful next test is whether a final proposal specifies comparable product costs, measurable objectives and the authority needed to implement them. An external audit and management reporting answer different questions: one can examine historical records, while the other helps delegates compare future funding choices. A cheaper review can still be poor value if its scope is unclear; internal reporting can be useful without independently assuring its inputs.

The next evidence to watch is a final text, confirmed participation by any proposed service provider, a recorded vote and subsequent implementation records. This report makes no finding of financial wrongdoing, forecast of LDO returns or claim that either draft has secured community consensus.