A Compound DAO reserve wallet received 344,780 COMP at 09:46 UTC on May 5, fifty-eight minutes before the voting snapshot, according to on-chain reconstruction by Bitquery. The transfer gave Proposal 582's backers the narrow majority that cleared a $52 million V4 program budget later that day.

The wallet had already delegated its votes to the Compound Foundation, which publicly backed the proposal. Of the 3,757,805 total delegated votes at the snapshot, supporters cast 1,883,966, or 50.1%, with Tally recording no votes against.

What did the reserve purchase change?

Without the 344,780 COMP, the same supporters would have held 1,539,186 of a reduced 3,413,025-vote universe — 45.1%. That share would have left enough voting power outside the bloc to defeat the plan.

The margin was 0.1 percentage point. The plan would still have cleared its 400,000-vote quorum, but it would not have passed.

Bitquery published the wallet flow on its investigations page. The link between the reserves spent and the COMP received runs through a Binance account, and public chain data alone cannot prove the withdrawal's funding source.

How did the reserves get there?

Proposal 536, passed earlier, placed approximately 8.42 million DAI of legacy protocol reserves under Foundation stewardship. The proposal kept the assets DAO-owned and excluded discretionary trading and Foundation-specific expenses, citing protocol operations and governance continuity as the permitted uses.

The Foundation used that mandate to convert DAI into COMP. The tokens remained DAO property, but they arrived in a wallet whose votes were already pointed at the Foundation, turning the wallet into a vehicle for the same bloc the Foundation was already coordinating with.

What is the dispute?

Forum delegate ugurmersin alleged on Sept. 27 on the Compound governance forum that the conversion and delegation breached the reserve mandate. The post is titled "Misappropriation of the v2 DAI reserves by the Compound Foundation."

The Foundation's Sept. 28 statement on the forum said the conversion was "consistent with the mandate's governance-continuity purpose," that the COMP remained DAO-owned, and that none of the assets had been spent on Foundation operations.

The Foundation reads the mandate as covering any action that preserves the DAO's ability to coordinate governance. The delegate reads it as covering only operations the Foundation had been running, not the acquisition of new voting weight. The mandate named protocol operations and governance continuity, and referenced no explicit authority to convert reserves into additional votes.

What did Proposal 582 actually fund?

Proposal 582 designated $14 million of the $52 million total to a Foundation-controlled operational wallet. It placed the remaining $38 million with a Treasury Management Committee pool, with releases tied to milestones.

The vote outcome is on-chain and settled. The authority to make the conversion that delivered that outcome is not. The dispute now turns on a narrow reading of "governance continuity" — and on whether the DAO will treat a future use of reserves for vote acquisition as inside or outside the line.

Compound has not signaled any plan to revisit Proposal 582 or to claw back the operational wallet funding. The Foundation's Sept. 28 post closed by inviting further forum dialogue. Any binding test of the mandate's scope would require a new proposal, a new snapshot, and the same bloc the May 5 purchase was calibrated to tip.