For DAOs, the biggest risk is no longer only a smart contract bug. The real risk grows when treasury access, delegation power, and emergency controls are not transparent. Recent cases from Lido, Compound, and Ampleforth show that without strong proposal review, timelocks, spending caps, and independent verification, DAO governance can become weak.

A DAO’s real strength is not only in its code. It is in its decision making process: who can move treasury funds, who controls votes, and who can take special powers during an emergency.

Every DAO treasury proposal should face three questions:

• Is the budget math clear?

• Is the beneficiary alignment clear?

• Are veto or emergency controls transparent?

These are the core issues in both the Lido and Compound cases.

In Compound, the Foundation used protocol reserves to buy $52 million worth of COMP. Delegates argued that this breached the reserve mandate because it could increase the Foundation’s governance voting power.

The data shows that Proposal 582 approved a $52 million budget. Of this, $14 million was for a Foundation controlled operational wallet and $38 million was for a Treasury Management Committee pool. Releases were tied to milestones.

According to Bitquery, 344,780 COMP pushed supporters above half of delegated voting power. This is the real concern: if treasury bought tokens can be delegated for voting, treasury control can quietly become governance control.

Imagine a DAO has a $100 million treasury. The Foundation says, “We will buy $10 million of governance tokens, but the tokens will stay owned by the DAO.”

Technically, the DAO owns the tokens. But if those tokens are delegated for voting, the Foundation may gain practical voting influence. The real question is not who owns the tokens on paper. The real question is who controls their voting power.

In Ampleforth, a wallet submitted Proposal 54 asking for 2.5 million USDC to be sent to itself. The treasury dashboard showed about 2.54 million USDC, so the request was equal to about 98.5% of the USDC balance.

Just before the proposal was submitted, an address delegated 87,238.5461 FORTH voting power to the proposing wallet. The proposal was canceled, votes stayed at zero, and no transfer was executed.

Imagine a community group where one member suddenly receives a very large amount of voting power. That member proposes moving almost the entire group bank balance into their own account. If the voting threshold is low and the review process is weak, the proposal could pass.

This did not happen in Ampleforth because the proposal was canceled. But it shows why delegation power and proposal thresholds need careful design.

Lido DAO is discussing whether its 2027 grant budget should be linked to LDO token purchases. The concern is that genuine savings could flow directly into an LDO buyback engine, making the real purpose of the budget unclear.

In Lido’s NEST system, measured staking revenue is compared with a daily baseline of $109,589, or about $40 million per year. When revenue falls below the baseline, a negative counter increases. Extra revenue should first repair any shortfall before new allocations begin.

At the Oct. 13 checkpoint, the counter was minus $564,230.96 and the allocation was skipped. The 2026 grant request used a $43.8 million baseline, while the first half report referenced $41 million and projected $37.7 million in full year expenses.

Suppose a DAO says, “Whatever costs we save will go into token buybacks.”

That sounds good. But if the definition of savings is unclear, a team can create a large budget, show a smaller actual spend, and then trigger buybacks. This is why budget baselines, revenue sources, assumptions, and spending caps must be public.

Emergency controls are necessary. If there is an exploit, oracle failure, or governance attack, a protocol needs the ability to act fast. But emergency power without limits can become a backdoor.

A good emergency system should have:

• Clear trigger conditions.

• Limited allowed actions.

• A time bound emergency period.

• Public disclosure.

• A post incident review.

• A veto from the community or security council.

• Accountability if powers are misused.

Emergency control should not mean that the core team always keeps control. It should mean that only necessary actions are taken during an emergency, for a limited time, with full transparency.

Before voting on any DAO treasury proposal, use this checklist:

• Does the proposal state the exact amount and receiver?

• Is the money going to one team, foundation, or wallet?

• Are the deliverables measurable?

• Is there a spending cap?

• Is the use of funds restricted?

• Is there a timelock?

• Can emergency withdrawals happen?

• Is there a conflict of interest between the proposer and beneficiary?

• Will there be an independent audit or review?

• Does the community have a veto or rollback option?

• Will there be a public report after spending?

If most answers are no, the community should pause before approving the proposal.

Over the next 6 to 12 months, the main DAO governance debate will shift from token price and yield to treasury control. After cases like Compound, more DAOs will create clearer rules for foundation powers, reserve mandates, and voting token purchases.

My prediction is that three changes will become common in major DAOs:

• Stricter spending caps and longer timelocks for treasury withdrawals.

• Clear limits on voting power held by foundations or core teams.

• Public trigger conditions and post action reviews for emergency powers.

As DeFi TVL recovers, treasury sizes will also grow. That means the financial impact of governance attacks will become larger. DAOs that do not build transparent treasury frameworks now may lose both community trust and institutional capital later.

• Compound DAO $52 million COMP purchase and mandate dispute: https://cryptoslate.com/compound-dao-used-protocol-reserves-to-buy-52-million-worth-of-comp-and-delegates-call-it-a-mandate-breach/

• Ampleforth $2.5 million USDC proposal cancellation: https://cryptoslate.com/defi-governance-gap-allows-one-wallet-to-request-98-of-ampleforth-treasurys-usdc-balance/

• Lido DAO budget review and LDO buyback flaw: https://cryptoslate.com/lido-dao-exposes-token-flaw-and-forces-a-budget-review/

• Compound voting impact data: https://coinmarketcal.com/news/compound-dao-s-52m-comp-purchase-swung-a-governance-vote-data-shows

• Ampleforth proposal timeline: https://daotimes.com/one-wallet-almost-pulled-98-of-ampleforth-treasurys-usdc-before-a-last-minute-cancellation/