Compound DAO used protocol reserves to buy 344,780 COMP tokens worth roughly $52 million, then delegated the tokens to the Compound Foundation. On-chain data shows the COMP arrived in a DAO reserve wallet just 58 minutes before a May 5 snapshot that fixed voting power for Proposal 582, and that single transfer pushed the Foundation-aligned bloc over the 50% threshold it needed to control the outcome.
How the transfer flipped the vote math
Bitquery recorded the 344,780 COMP landing in the DAO reserve wallet at 09:46 UTC on May 5. The snapshot came 58 minutes later. At that moment, the wallet had already delegated its voting power to the Compound Foundation, which backed the proposal.
The timing matters because of the numbers. At the May 5 snapshot, total delegated voting power stood at 3,757,805 votes. The COMP transfer gave Foundation-aligned delegates 1,883,966 votes, exactly 50.1% of the total. That margin was razor-thin: Proposal 582 cleared the 50% threshold by just 0.1 percentage point.
Without the reserve-wallet COMP, the same supporters would have held 1,539,186 votes out of a reduced 3,413,025-vote total — 45.1%. That would have left enough voting power outside the bloc to defeat the plan.
Proposal 582's $52 million budget and what it funds
The $52 million figure describes an approved V4 program budget, not a single lump-sum payment. Proposal 582 designated $14 million for a Foundation-controlled operational wallet and $38 million for a Treasury Management Committee pool. Releases from those pools are tied to milestones.
The proposal passed with zero votes against, despite the controversy over how the COMP was acquired. Tally recorded roughly 1.88 million votes in favor and none opposed. The plan would still have cleared its 400,000-vote quorum even without the reserve-wallet COMP — but the outcome could have differed if the reserve COMP had not been in the snapshot at all.
The disputed link through Binance
The path from spent reserves to received COMP runs through a Binance account. Public chain data alone cannot prove which funding account was used for the withdrawal, leaving a gap that the Foundation and its critics interpret differently.
On Sept. 27, Compound forum delegate ugurmersin alleged that the conversion and delegation breached the reserve mandate. The Foundation responded on Sept. 28, saying the conversion was consistent with the mandate's governance-continuity purpose. It added that the COMP remained DAO-owned and that none of the assets had been spent on Foundation operations.
That back-and-forth centers on Proposal 536, an earlier measure that placed approximately 8.42 million DAI of old protocol reserves under Foundation stewardship for protocol operations and governance continuity. Proposal 536 kept the assets DAO-owned and explicitly excluded discretionary trading and Foundation-specific expenses. The Foundation and the delegate disagree over whether converting those reserves into voting power fit within those limits.
Governance authority remains contested
The May vote's outcome is settled. Proposal 582 passed, the budget is approved, and the COMP sits in a DAO-owned wallet. What isn't settled is the authority to make the conversion in the first place.
The on-chain reconstruction shows that the COMP acquired through DAO reserves constituted a majority of all delegated voting power at the May snapshot — the very snapshot that determined Proposal 582's fate. That fact alone doesn't resolve whether the acquisition was permitted under Proposal 536's terms. It does explain why the vote passed with zero opposition and why the Foundation's Sept. 28 response has not closed the dispute.
The Foundation says the assets weren't spent on its own operations. Ugurmersin says the conversion breached the reserve mandate. Both sides agree the COMP stayed DAO-owned. The disagreement is about process and permission, and it's still open on the Compound forum.
