Compound delegate says COMP reserve buy breached mandate; Foundation disputes claim
In brief
- Delegate ugurmersin alleged Sept. 27 that converting reserves to COMP breached Compound's reserve mandate.
- Compound Foundation said Sept. 28 the COMP stayed DAO-owned and served governance continuity.
- Bitquery reported 344,780 COMP reached a DAO reserve wallet 58 minutes before the May 5 snapshot.
- Chain data alone can't prove which account funded the Binance withdrawal behind that COMP.
- Proposal 582 passed with zero votes against; $52 million was an approved V4 program budget.
What the chain data shows
The details here are as reported by CryptoSlate, which cites Bitquery's on-chain reconstruction. Bitquery counted 1,883,966 votes eventually cast for the plan out of 3,757,805 total delegated votes at the May 5 snapshot. That's 50.1%. Other delegates couldn't have outvoted supporters even if every one of them had voted no.
The reserve wallet is the key piece. It had delegated its votes to the Compound Foundation, which backed the plan, and without its 344,780 COMP the same supporters would've held 1,539,186 of 3,413,025 votes (45.1%), leaving enough voting power outside their bloc to defeat it.
There's a real caveat. The link between the reserves spent and the COMP received runs through a Binance account, and public chain data alone can't prove which account funded that withdrawal.
The result itself didn't change.
Proposal 582 passed with zero votes against. Tally recorded roughly 1.88 million votes for it, so the plan would still have cleared its 400,000-vote quorum without the reserve-wallet COMP.
Where the $52 million figure comes from
CryptoSlate says the $52 million figure describes an approved V4 program budget. Proposal 582 designated $14 million for a Foundation-controlled operational wallet and $38 million for a Treasury Management Committee pool, with releases tied to milestones.
The mandate dispute
The authority question goes back to Proposal 536, which placed approximately 8.42 million DAI of old protocol reserves under Foundation stewardship for protocol operations and governance continuity. It kept the assets DAO-owned and excluded discretionary trading and Foundation-specific expenses.
Delegate ugurmersin alleged on the Compound forum that the conversion and delegation breached that mandate. The Foundation's response said the conversion was consistent with the mandate's governance-continuity purpose, that the COMP remained DAO-owned and that no assets were spent on Foundation operations.
So the vote's settled. Whether the Foundation had the authority to make that conversion isn't, and it's reopened a wider fight over how DAO assets get used in governance. COMP was down 3.31% over 24 hours and ranked #131 by market cap when CryptoSlate published.
Frequently asked questions
Did the reserve-wallet COMP change the outcome of Compound Proposal 582?
No. Proposal 582 passed with zero votes against. Tally recorded roughly 1.88 million votes for it, so it would still have cleared its 400,000-vote quorum without the 344,780 COMP from the reserve wallet. What changed is that supporters held 50.1% of delegated voting power at the snapshot, versus 45.1% without that COMP.
Why does the delegate say the Compound Foundation breached its mandate?
Proposal 536 placed about 8.42 million DAI of old reserves under Foundation stewardship for protocol operations and governance continuity, while excluding discretionary trading and Foundation-specific expenses. Delegate ugurmersin alleged that converting reserves to COMP and delegating it breached that mandate.
How did the Compound Foundation respond to the allegation?
In a Sept. 28 response, the Foundation said the conversion was consistent with the mandate's governance-continuity purpose, that the COMP remained DAO-owned, and that no assets were spent on Foundation operations. The authority for the conversion remains contested.
