Compound DAO is facing a major governance controversy. Community member ugurmersin has accused the Compound Foundation of using 8.42 million DAI from DAO reserves to purchase 344,780 COMP tokens, then using those tokens to influence votes on two key proposals.

The proposals in question:

• Proposal 580: Transfer nearly all DAO funds to a Treasury Management Committee (TMC)

• Proposal 582: Approve a 52 million dollar V4 program budget for the Foundation, including 14 million dollars in Foundation-controlled operational wallet and 38 million dollars in TMC-managed reservecryptopolita.

The central question: Did the Foundation violate the mandate of Proposal 536?

In February 2026, Proposal 536 passed. Under this proposal:

• 8.42 million DAI was placed under Foundation management

• These funds were for protocol operations only

• Speculative trading or use for Foundation's own operations was prohibited

• Funds would remain entirely under DAO ownershiptoken.

ugurmersin alleges that converting DAI to COMP on an exchange and using it for voting power violates this mandate.

According to the allegations, on-chain records show:

1. 8.42 million DAI was transferred from Foundation-managed Safe to an exchange

2. On the exchange, this DAI was swapped for 344,780 COMP tokens

3. These COMP tokens were delegated to the Foundation's voting address

4. 58 minutes before voting ended, these COMP tokens were transferred back to the Safethede.

This timing is critical. The increase in voting power pushed Proposal 582 supporters' delegated voting power from 45.1 percent to 50.1 percent.

Compound Foundation has denied these allegations. They state that:

• Proposal 582 had enough votes even without the additional COMP from the Foundation. Both proposals already had sufficient support.thede.

• Proposal 536 does not have an explicit treasury management program, but it does allow the Foundation to maintain sufficient COMP availability for protocol components (such as reward distribution and governance execution).

Still, the community question remains: Is converting reserves to COMP to increase voting power against the spirit of the DAO?

This controversy raises several serious questions about treasury control in Compound DAO.

Proposal 536 stated that funds were for protocol operations. But is buying governance voting power a protocol operation?

If the Foundation is allowed to buy COMP from reserves, can any future foundation or committee do the same?

Does this create a permanent governance advantage?

Under Proposal 580, nearly all DAO funds moved to TMC control. But Foundation signers are included in the TMC.protos+1

This means:

• Foundation bought COMP from reserves

• Used that COMP to increase voting power

• Used that voting power to give control to TMC

• Foundation signers are on TMC

• TMC now controls nearly all DAO funds

This raises questions about circular control.

The V4 program budget includes:

• 14 million dollars Foundation-controlled operational wallet (for one year of development)

• 38 million dollars TMC-managed reserve.

Some delegates argue this budget benefits the Foundation, since the Foundation will execute V4 development and Foundation signers are also on the TMC.

The biggest red flag is timing.

COMP tokens were transferred back 58 minutes before voting ended.token.

This timing raises questions:

• Was this pre-planned?

• Should the community have been informed beforehand?

• Is temporary voting power increase ethical?

This controversy provides critical lessons for all DAOs. Here are concrete safeguards that can help prevent similar disputes in the future.

Every treasury proposal must include:

• Exact purpose of funds

• Clear list of allowed activities

• Clear list of prohibited activities

• Specific reporting requirements

• Sunset clauses or renewal conditions

• Independent audit requirements

For example, a treasury mandate should explicitly state whether funds can be used for:

• Buying governance tokens

• Providing liquidity

• Staking or yield farming

• Emergency reserves

• Operational expenses

• Grants and incentives

Ambiguity creates room for interpretation, and interpretation creates controversy.

When the same people control both treasury and voting power, conflict of interest arises.

DAOs should consider:

• Prohibiting treasury managers from using treasury assets for voting power

• Requiring separate governance processes for treasury decisions

• Implementing higher quorum or supermajority requirements for treasury transfers

• Creating independent treasury oversight committees with community representatives

• Mandating that treasury assets cannot be delegated to voting addresses without explicit community approval

Any movement of treasury assets should be announced to the community in advance.

Required practices:

• Minimum 48 to 72 hour pre-announcement before any treasury asset movement

• Public dashboard showing all treasury wallet addresses and balances

• Real-time tracking of voting power changes related to treasury assets

• Detailed explanation of purpose before any treasury-to-exchange transfer

• Post-transaction reports within 24 hours of execution

Transparency is not optional. It is the foundation of trust.

When foundations or core teams control treasury, independent oversight mechanisms are essential.

Recommended structures:

• Community-elected treasury auditors with on-chain monitoring tools

• Delegate watchdogs with authority to request treasury reports

• Regular (monthly or quarterly) treasury transparency reports

• Third-party audits of treasury movements annually

• Public forum for community questions and treasury discussions

• Clear process for raising treasury misuse allegations

To prevent last-minute voting power manipulation:

• Implement a 7 to 14 day cooling-off period between treasury asset movement and related votes

• Prohibit using newly acquired governance tokens from treasury for votes within 30 days of acquisition

• Require disclosure of all treasury-backed voting power at least 5 days before any vote

• Create a public registry of all treasury-controlled governance tokens and their delegation status

No single entity should control too much treasury power.

Safeguards:

• Cap the percentage of total treasury that any single committee or foundation can control (for example, maximum 40 percent)

• Require multi-signature wallets with diverse signers (community delegates, independent experts, foundation members)

• Diversify treasury assets across multiple chains and asset types to reduce single-point risk

• Implement gradual deployment schedules rather than lump-sum transfers

Give the community a way to pause controversial treasury actions:

• Allow a certain percentage of token holders (for example, 5 percent) to trigger a 7 day pause on treasury transfers

• Create a community review period for any treasury proposal above a certain threshold (for example, above 10 million dollars)

• Implement emergency pause functions that can be activated by independent security councils or community-elected guardians

Anyone involved in treasury decisions must disclose conflicts:

• Foundation team members must disclose their compensation and incentives related to treasury proposals

• Treasury committee members must disclose any personal holdings that could be affected by treasury decisions

• Delegates voting on treasury proposals must disclose any financial relationships with proposal beneficiaries

• All disclosures should be public and on-chain where possible

After treasury proposals are executed:

• Conduct a post-implementation review within 90 days

• Compare actual outcomes with proposed objectives

• Publish findings publicly

• Create a process for correcting course if outcomes diverge significantly from proposals

• Hold treasury managers accountable for misrepresentation or misuse

Many treasury controversies arise from lack of understanding.

DAOs should invest in:

• Regular treasury education sessions for community members

• Simple explainer documents for complex treasury proposals

• Community AMAs (Ask Me Anything) before major treasury votes

• Translations of treasury proposals into multiple languages for global communities

• Treasury dashboards that non-technical users can understand

Compound DAO is not the first DAO to face treasury controversy, and it will not be the last. But other DAOs can learn from this situation.

Lido recently implemented Dual Governance, giving stETH holders veto power over LDO governance decisions. This is a step in the right direction, but treasury control should also be part of this protection. stETH holders should have visibility and input on how Lido treasury is managed, since their staked assets are ultimately at risk.

Arbitrum DAO recently launched its Watchdog program to address grant misuse. This model could be extended to treasury oversight. A Treasury Watchdog could monitor treasury movements, flag suspicious activities, and recommend investigations when needed.

Aave is currently debating V4 proposals that involve significant treasury commitments. The Compound controversy should serve as a reminder to implement clear treasury safeguards before passing large budget proposals.

Uniswap has one of the largest treasuries in DeFi. As governance discussions continue around fee switches and treasury deployment, clear mandates and independent oversight will be critical to maintain community trust.

Every DAO should ask itself:

• Who controls our treasury?

• What rules govern treasury usage?

• Can treasury assets be used for voting power?

• Is there independent oversight?

• Can the community pause or veto controversial treasury actions?

• Are treasury movements transparent and trackable?

If the answers are unclear, it is time to fix them before a controversy arises.

So far, the Foundation has provided a public response, but the controversy continues.

Possible outcomes:

1. Community investigation: Delegates and community members may conduct an independent review of on-chain data

2. New proposal: A proposal with new treasury control safeguards may be introduced

3. Foundation response: The Foundation may provide a detailed explanation or clarification

4. Governance reform: Compound DAO may implement broader treasury governance reforms

Regardless of the outcome, this controversy has already changed how the community thinks about treasury control.

The Compound DAO controversy shows that passing a proposal is not enough. Process, timing, transparency, and community trust are equally important.

Treasury control is the most sensitive area of DAO governance. When funds are used to increase voting power, community trust can break, even if the proposal is technically legal.

DAO governance is not just about following rules. It is about following the spirit of the rules.

Other DAOs should not wait for their own treasury controversy to implement safeguards. Learn from Compound. Build transparency. Create oversight. Protect community trust.

Because in the end, a DAO without trust is just a wallet with a voting interface.

1. Protos: Compound Foundation accused of misappropriating DAO funds

2. Cryptopolitan: Compound accused of diverting 8.4 million dollars in DAO reserves into COMP

3. TokenPost: Compound Foundation accused of using 8.42 million DAI to buy COMP

4. TokenPost: Compound community member accuses Foundation over 8.42 million DAI reserve

5. TokenPost: Compound reserve wallet gets 8 million dollars in COMP before DAO vote

6. Crypto Economy: 8.4 million dollars Compound DAO reserve move sparks controversy

7. The Defiant: Compound Foundation denies V2 reserve misuse allegation

8. PANews: Compound Foundation stealing from itself

9. CoinMarketCap: Latest DAI news update

10. Compound Forum: Compound Treasury Consolidation proposal

#CompoundDAO #DAOGovernance #TreasuryManagement #DeFi #Web3Governance #DAOResearch #MconnectDAO #India #BlockchainGovernance #Tokenomics #GovernanceRisk #Decentralization #DAOSafety #TreasuryOversight #CommunityTrust