Funding and Mandating an Independent Web3 Financial Audit & R&D Expenditures

1. Executive Summary

Following the community proposal (https://research.lido.fi/t/mandating-a-2-year-financial-audit-demand-for-product-r-d-and-payroll-transparency/) published on the Lido Governance Forum on October 13, 2026, the Core Team and Finance Workgroup were issued a 14-day proposal to deliver an itemized financial report for the 2024–2026 operational period.

Due to the internal team’s failure to provide the requested financial reporting detailing the exact incubation costs, development expenditures, and the overall return on investment (ROI) of new initiatives, this Snapshot vote formally mandates the Lido DAO to bypass internal channels.

This proposal authorizes the allocation of treasury funds to contract an elite, independent Web3 forensic accounting and auditing firm to execute a comprehensive, external financial investigation.

2. Audit Scope & Deliverables

The selected external Web3 accounting firm (prioritizing Convoy Finance, Llama, or Fox Audit) will be contracted to deliver a public, itemized report covering the following areas:

• Financial Forensic of R&D & Incubation Costs: A complete on-chain and off-chain ledger of every dollar, LDO, and ETH allocated to the research, development, smart contract audits, and deployment of Lido Earn, stVaults, and Wisp,Lido Lend etc.

• Granular Payroll & Overhead Breakdown: A fully audited, anonymized breakdown of all contributor salaries, bonuses, retention packages, and contractor fees funded by the Lido Treasury over the past 24 months. This includes exact figures spent on marketing, administrative, and legal overhead for sub-products.

• Product Performance & Revenue Review: An independent financial review of the historical on-chain revenue generated by these products versus their upfront deployment costs to evaluate real economic performance.

3. Financial Allocation & Execution Mandate

To ensure maximum financial safety, eliminate conflicts of interest, and guarantee execution, the following procurement rules apply:

• Budget and Cost-Efficiency: To ensure competitive pricing, this proposal authorizes a target budget of up to $150,000 USD, with a hard maximum cap of $400,000 USD (payable in USDC, USDT, or ETH equivalent) to guarantee that a full, unrestricted audit can be completed by top-tier firms.

• Fund Custody: No funds shall be moved or disbursed to any internal party or unverified wallet upon the passing of this vote. The approved budget will remain securely within the Lido Treasury (Aragon Agent) until a formal service agreement (SOW) is negotiated.

• Independent Procurement Mandate (Steakhouse Financial): @steakhouse Financial is formally appointed by the DAO to act as the sole independent negotiator. Steakhouse Financial will collect bids from the designated pool (Convoy/Llama/Fox), evaluate their methodologies, ensure cost-optimization, and select the final execution partner. And announce the selection results, timelines, and price in the relevant forum thread.

• Direct-to-Auditor Payment (TMC): Upon final vendor selection by Steakhouse Financial, the Treasury Management Committee (TMC) is authorized to execute the transaction directly from the Treasury to the verified corporate wallet of the selected auditing firm (e.g., 50% upfront, 50% upon public delivery of the final report).

4. Implementation Timeline & Cooperation

• Procurement Phase (Days 1–7): Steakhouse Financial will conduct negotiations and finalize the contract within 7 days of this vote passing.

• Audit Execution Phase (Days 8–68): The contracted firm will be given exactly 60 calendar days to complete the investigation and post the unedited final report directly to the Lido Governance Forum.

• Operational Alignment: Lido Labs leaderships along with the Finance Workgroup, will provide the selected external auditors with the necessary operational data, internal ledgers, and technical documentation required to complete the report in accordance with this approved DAO mandate.

5. Pre-Voting Review & Feedback Period

To ensure maximum consensus and allow all ecosystem participants to voice their perspectives, this proposal will remain open for community discussion on the Lido Governance Forum for exactly 10 calendar days prior to the activation of the official Snapshot vote.

* During this 10-day window, delegates and community members are encouraged to submit feedback, request clarifications, or suggest structural amendments.

* Constructive changes supported by the community consensus will be integrated into the final text before voting begins.

2 Likes

Before any questions about the price arise, let me share a quick thought: this cost amounts ($150 000 - $400 000) just 0.4–1% of the team’s total annual expenditure.

In my view, if a team can afford to build products that operate at a loss, develop buyback mechanisms that don’t actually work, or cover losses for other projects following a hack, then allocating 1% of their budget shouldn’t be an excessive burden.

Team are constantly told about transparency, yet there is no sign of it in the reports.

In its first 1–3 years, any business typically operates at a loss or breaks even; in subsequent years, it begins to generate profit—with that profit growing over time. In the case of Lido, however—after nearly six years of operation—we see only expenses amounting to $40 million per year. That seems rather strange, doesn’t it?

For this reason, a vote will be initiated on November 5, 2026.

I ask all delegates to vote HONESTLY.

If the audit reveals any questionable expenditures, we will look into them. If everything is above board, it will further demonstrate the project’s transparency to the market and the public—and it might even highlight additional expenses that could be cut to free up capital.

LDO is not a tool for infinite grants; it is a governance token that must accrue value. If the R&D doesn’t generate ROI for the DAO, the spendings must be reviewed immediately.

1 Like

5 days to voting.

Still waiting for constructive response.

I think you are conflating financial accounting assurance with managerial capital allocation.

Lido Labs, the DAO, etc. are all very transparent. I do not think we are questioning whether the books are true, whether transactions match invoices, or whether there is fraud, misappropriation or embezzlement. In fact the complete opposite we know is true.

Steakhouse publish frequent reports, models, etc. All backed up by Dune dashboards and onchain data. Furthermore sharing individual and granular salaries of contributors is dangerous. We already know from a breakdown of total costs per contributor that contributors are paid at market rate.

The outcome of a detailed audit = $400k wasted. Excluding wasted time by contributors. And nothing will have changed.

Traditional companies esp those in a growing phase don’t use audits to solve problems regarding TAM, PMF, etc and it’s not uncommon for projects to operate at a loss by design. Although I am not suggesting Lido do that.

If you wanted to move the needle i’d consider focusing on customer acquisition costs by product lines within Lido. “staking” “vaults” etc, and frankly the only one worthy of that is staking which is not growing. All other product lines are in phases discovering PMF which requires incubating upfront capital. One could also consider hurdle rates and sunset thresholds on new product lines.

TLDR: I do share the underlying concern of high costs similar to the vast majority of projects in this industry, but Lido DAO has already begun reducing costs and should continue to do so via the methods I briefly touch on above. I do not support this proposal in going on an expensive and costly witch hunt via a granular financial audit.

My recommendation: if you are unsatisfied with the ROI then look at GOOSE and EGG strategically and their budget cycles and work within those proposals to ensure tighter spending, however, be careful that doesn’t come at the cost of any ROI. At the end of the day Lido DAO needs to increase its TAM and find PMF more than anything else.

5 Likes

We support greater transparency around Lido’s spending, but we don’t see sufficient justification for allocating $150–400k to this audit.

The proposal combines financial verification, payroll review, and product performance assessment without a clearly defined scope, cost estimates, or confirmed agreement from Steakhouse to take on the proposed role.

We suggest first identifying which questions remain unanswered by the existing financial reports and which of them actually require independent verification. From there, the DAO can discuss a specific scope, auditor, and budget.

We’re not opposed to an independent audit in principle, but cannot support the proposal in its current form.

2 Likes

Hi Leuts,

Thanks for the detailed feedback. I appreciate your point regarding product-market fit and the fact that incubating new product lines requires upfront capital and a phase of operating at a loss.

However, the core issue here isn’t the concept of investing in growth—it is the complete lack of visibility into the efficiency of these investments. While Steakhouse reports and Dune dashboards are excellent for tracking high-level on-chain data, they don’t give the DAO a granular view of the managerial capital allocation. We see a flat $40M annual burn rate, but we cannot evaluate the specific ROI of sub-products like Lido Earn, stVaults, or Wisp.

Regarding contributor compensation: the goal is explicitly not a witch hunt or the de-anonymization of individuals. The proposal specifically mandates an anonymized breakdown. The intent is to evaluate whether the collective overhead of these product teams matches their real economic performance.

Working within GOOSE and EGG budget cycles is a great suggestion, but to tighter spend effectively, the DAO needs a baseline of hard, independent data. Allocating up to 1% of the annual budget to audit and optimize how the other 99% is spent is a standard governance practice that can ultimately save the DAO millions.

1 Like

Hi cp0x team,

Thank you for sharing your stance. I’m glad to hear that you support greater transparency around Lido’s spending in principle. Your critique regarding the combined scope and the need for a confirmed agreement from Steakhouse is entirely fair—these are structural details that definitely warrant refinement.

This proposal was initially designed to establish a fundamental mandate from the DAO: “Do we want an independent external audit?” If the community agrees on the principle, we lock in a conservative budget ceiling and iron out the specific logistics.

I completely agree with your suggestion to first pinpoint the exact “blind spots” that existing financial reports leave unanswered. Let’s do exactly that right here in this forum thread.

As a compromise, we can delay the Snapshot vote to:

1. Formulate a precise checklist of questions regarding R&D and incubation costs that are currently unaccounted for.

2. Reach out to Steakhouse Financial to gauge their willingness and capacity to step into the independent negotiator role.

3. Streamline the audit scope lfor instance, narrowing it down strictly to R&D expenditures and sub-product ROI, which would naturally lower the target budget.

From your perspective, which specific spending areas or product lines do you feel are currently the least transparent and should be prioritized?

1 Like

I think Leuts and Cryp1 both have a point here. We need better spending efficiency, but it’s hard to judge that without knowing what each product actually costs.

I brought up budget transparency in my NEST proposal too.

EGG 2027 is coming up, so why not sort this out now? Show planned spending by product, what we’re expecting to get for it, and then track actual costs in quarterly reports.

Would be much better to agree on this before the budget is ready, rather than argue about missing details afterward.

1 Like

One thing that I really like about the Lido DAO community is that people have strong opinions on how to improve the protocol, the management and the DAO’s business.

I understand the spirit of this proposal to be a request for greater accountability, clearer visibility into spending, and better capital allocation so that the DAO can address losses and build a sustainable, profitable business.

Because of the DAO not turning a profit and the token plumetting in value, the DAO has been faced with backlash and tokenholders’ activism to change the downward trajectory of both business and token value.

I could not be more supportive of this, as a tokenholder and Delegate who also wants the success of Lido.

Nevertheless, I believe the recent wave of requests for better financial transparency don’t do much to improve the business and might even distract the team from the core mission, which is our success.

The information that companies use to take decisions are wider than just financial; there is strategic and commercial information, product and technical info, personal (staff), operational and of course legal and security considerations. Most of the proposals lately have been around the financial aspect of it: Tighter coupling between token price and revenue (NEST and extraordinary measures), tighter financial scrutiny… It is true that financial transparency is key for the DAO members to understand the picture, the reality of it is that Lido is already very transparent in comparison with other companies and the transparency proposals like this one come at a reduced marginal benefit: it costs a lot more to be 10% more transparent and I don’t believe we can take better decisions as DAO tokenholders with this information. Note that I’m not against more financial transparency, just not on spending 150-400k on an unscheduled flash audit that distracts everyone’s already set priorities.

So… is there a way to actually get a better understanding and increase the trust in the management decisions taken? I believe there is.

In order for tokenholders to better understand management and the contributors’ perspective, there are still a lot of unknowns besides the financials and I suggest we work on making these more transparent.

Currently we have one quarterly Lido Poolside update that tries to condense a lot of the non financial information on strategy, operations, ecosystem, etc. There is a lot of info to be transmitted in very little time, so we don’t get a lot of that information, and the QnA is reduced.

I suggest a higher frequency of open communication forums like the Poolside with an agenda that is pre-built by the tokenholders. I am not sure about the needed frequency but maybe monthly, with specific questions from the tokenholders submitted at least a week in advance so the team has time to prepare the answers properly.

I agree with @cryp1, we need more information, but I believe the type of information that we need isn’t financial.

Edit: Sorry I missed your suggestion @Kuzmich . I agree with you in the fact that despite my focus on other types of information beyond just financial, we can get better financial information. That said, let’s determine what we would need in advance and include it. This way, the effort to provide it is budgeted.

1 Like

Hi Kuzmich,and thanks for your post

For quarterly reports to be truly effective, we first need a clear, agreed-upon methodology for accounting for R&D costs. Right now, without an independent perspective on how exactly resources are allocated across sub-products, it will be difficult for us to verify this quarterly data.

How would you feel about bringing in external experts (perhaps someone like Convoy or Llama) as part of the preparations for EGG 2027? The goal wouldn’t be a “punitive” audit of the past, but rather the creation of a transparent R&D reporting architecture for the future. This would save on the budget while addressing both objectives.

2 Likes

Thanks for the detailed feedback. I agree that more frequent Poolside Q&A sessions with a community-driven agenda would be an excellent tool for operational alignment, and we should definitely implement that.

However, we need to separate the formats here. While Q&A sessions are great for discussing high-level strategy and PMF, they cannot replace hard product analytics. It is incredibly difficult for token holders to ask the right questions during a live call if we don’t have a granular breakdown of the actual ROI for specific sub-products—whether it’s Lido Earn or stVaults.

I’ve taken the feedback regarding a blurry scope and high costs . This is why I am holding off on the Snapshot vote to refine the proposal. We can narrow the scope strictly to an independent R&D and product efficiency audit. This will address the high-cost argument while still delivering the hard, unbiased data on ROI and performance that Lido DAO team and token holders urgently need.


1 Like

i read the q1 and h1 reports and found a few gaps that i think could be a good intermediary between 3rd party audit and continuing as is if thats the direction this takes:

  • team pay isn’t shown as a number. H1 report spreads contributor pay across its product cost lines and never gives a total..
    • ideally: one quarterly total for team pay, cash plus tokens in dollars, split by product or function, with headcount. obviously anonymized individual is more trasnparent but has drawbacks too
  • you cant see budget versus actual by line. H1 says “a direct reconciliation to EGG budgets per line is not possible.”
    • q1 report did show the percentage used for each budget line
  • The KPIs aren’t tied to their cost
    • H1 marks three goals off track:
      • staking market share, down from 23.9% to 21.2%
      • stVaults, at 5,768 ETH
      • Lido Earn, at $0.54M a year
      • never restates the original targets: stVaults was expected at 1M ETH and is now aimed at about 100k, and Earn was expected at $8M a year.
    • the report doesnt tie each goal to what was spent on it
1 Like

Hi, @kb1900

Thank you for the details

. I expect to put a new proposal by the beginning of next week, incorporating all the revisions and points raised by the delegates, and will then submit it for further discussion.

1 Like

I have prepared two versions of the initial proposal, incorporating feedback from the delegates. Please @cp0x @Leuts @Kuzmich @Lanski take a look and provide some constructive input.

Version 1

Funding and Mandating a Targeted Web3 Financial Audit of R&D Expenditures for EGG 2027 Planning

1. Executive Summary
Following up on the discussion initiated on the Governance Forum, this proposal aims to establish a transparent foundation for the allocation of Lido DAO’s capital. Based on the feedback received from delegates and ecosystem participants, the initial initiative has been refined. Instead of a broad, extensive historical investigation, we propose focusing the audit strictly on the efficiency of R&D expenditures and sub-products. This approach will provide independent, objective data required for the high-quality formulation and optimization of the upcoming EGG 2027 budget cycle.

2. Audit Scope & Deliverables
A selected external Web3 firm (such as Convoy Finance, Llama, or Fox Audit) will provide a public report covering:

  • R&D & Incubation Costs: Tracking on-chain and off-chain expenses for products like Lido Earn, stVaults, and Wisp.
  • Product Efficiency: Assessing ROI and on-chain revenues against marketing and operational expenses.
  • EGG 2027 Architecture: Recommending a product accounting framework to tie future KPIs directly to specific product line costs.

3. Financial Allocation & Execution Mandate

  • Budget: Sets a target of up to $80,000 USD with a hard cap of $150,000 USD (in USDC, USDT, or ETH).
  • Negotiator Role: @steakhouse is requested to gather bids and select the auditor within 7 days; otherwise, the mandate shifts to the Treasury Management Committee (TMC).
  • Payments: TMC will disburse funds via a standard 50% upfront / 50% upon publication milestone structure.

4. Implementation Timeline & Cooperation

  • Days 1–7: Procurement and contract finalization.
  • Days 8–45: 37 calendar days for the auditor to complete the report and publish it on the forum ahead of the EGG 2027 budget approval.
  • Cooperation: Lido Labs and the Finance Workgroup will supply necessary operational data and documentation.

Version 2

Implementing Enhanced Financial Transparency, Strategic Communications, and Budget Optimization for the EGG 2027 Cycle

1. Executive Summary

Following up on the discussion on the Governance Forum, this initiative proposes an alternative compromise path that entirely eliminates treasury expenditures on third-party contractors. We agree with the arguments raised by delegates (Leuts, cp0x, Lanski) stating that an external audit is not the optimal solution and could distract the team from its core mission. Instead, we propose directing the internal resources of Lido Labs and the Finance Workgroup toward resolving specific methodological gaps in financial reporting, expanding non-financial communication channels, and optimizing expenditures in the upcoming EGG 2027 budget based on real product performance.

2. Budget Optimization and Capital Reduction in the EGG 2027 Budget

To address community concerns regarding return on investment (ROI), the following constructive adjustments are to be integrated into the draft EGG 2027 plan:

• Reduction of Core Operational Expenditures: A target reduction of the overall Lido Labs operational budget for 2027 by at least 10–15% compared to last year, achieved through the optimization of internal administrative processes.

• Tying Sub-Product Funding to Profitability (Hurdle Rates): А phased capital allocation system is introduced for sub-products (Lido Earn, stVaults, Wisp, etc.). The initial budget for these sectors for 2027 will be reduced by 30–50%. Funding expansion back to baseline levels will only become possible after the Finance Workgroup delivers a clear roadmap to break-even.

• Closure Criteria for Stagnant Initiatives : A mechanism for automatic funding reductions must be embedded within the EGG 2027 budget for product lines that fall significantly behind their initial targets. This decision is driven by the H1 report data highlighted by @kb1900 (stVaults sitting at 5,768 ETH instead of the planned 1M ETH; Lido Earn at $0.54M per year instead of the expected $8M; and a drop in overall staking market share from 23.9% to 21.2%). Capital must be redirected exclusively toward areas showing proven growth.

3. Resolving Methodological Blind Spots in Financial Reporting

To protect tokenholder interests, the internal finance teams commit to integrating the reporting standards proposed by @kb1900 into future disclosures:

• Transparency in Team Expenditures: Quarterly publication of the total aggregate contributor compensation (including LDO token incentives in USD equivalent), categorized by product functions and accompanied by anonymized headcount data.

• Line-by-Line Budget vs. Actual Reconciliation: A return to the Q1 report practice, which clearly displayed the budget consumption percentage for each individual EGG budget line. The phrase “a direct reconciliation to EGG budgets per line is not possible” from the H1 report will be permanently excluded from future reporting practices.

• Cost-to-KPI Mapping: Financial reports must directly couple allocated capital with achieved KPIs, allowing delegates to clearly see the real cost behind every fraction of a percent in market share or every single ETH in vaults.

4. Expanding Non-Financial Transparency and Strategic Communications (The Lanski Amendment)

Recognizing Lanski’s valid point that purely financial metrics do not reflect the full governance picture and that the community critically needs access to the team’s commercial, product, and operational logic, we require:

• Increased Frequency of Open Forums: Shift the Poolside communication sessions from a quarterly to a monthly format. This will ensure a continuous and high-quality dialogue between DAO participants and core contributors.

5. Next Steps and Integration

In order to achieve consensus and ensure a smooth transition to the updated governance model, the core Lido Labs team and the Finance Workgroup will thoroughly review this proposed option for the reduction and optimization of the EGG 2027 budget. This review will take into account everything written above, as well as the accumulated feedback from delegates, prior to presenting the final edition of the financial plan to the community for approval.

2 Likes

Thanks @Cryp1 . I’d love to respond immediately but I’m travelling and might take a few days. Hopefully during this weekend

1 Like

The most important thing Lido should do right now is cap its annual operating expenses at $30 million and consider how to allocate resources to grow the ecosystem within that budget.

Lido’s operating expenses should be capped based on its actual profitability. There needs to be a clear spending limit that reflects the protocol’s ability to generate revenue. Otherwise, continuously burning through funds is simply not sustainable.

2 Likes

The key issue with LDO is that there is no value capture in circulation — this is the practical problem that needs to be solved.

1 Like

I agree

LDO is showing one of the worst performances in the market.

However, I can’t influence anyone to vote for adding utility to the token, and the team has no interest in pursuing that.

1 Like