Compound governance is voting on Proposal 612, a change that would grant token holders the direct power to cancel pending Treasury Timelock operations and extend treasury waiting periods from two days to ten. A wallet that governance researcher Blockful links to Humpy has cast 1.75 million COMP in favor — more than all opposing votes combined and sufficient to clear the 400,000-COMP quorum.

The proposal, submitted Oct. 2 by delegate Ugur Mersin, remained active at about 2:25 p.m. ET on Oct. 5. The governance interface showed roughly 1.75 million COMP for, 921,000 against and no abstentions, according to the on-chain voting record on Tally.

What does the proposal actually change?

Mersin's forum proposal would give the Governor Timelock — the contract that executes approved governance decisions — both executor and canceller roles on the Treasury Timelock. A cancellation would still require a successful governance proposal, not a unilateral request from a single COMP holder.

The Treasury Escrow would receive a separate change: a ten-day withdrawal cooldown, with withdrawals expiring 17 days after initiation. That window gives governance more time to exercise its existing power to reclaim escrowed assets. The proposal does not add a mechanism for governance to cancel an individual escrow withdrawal.

The core issue is timing. Compound's current two-day treasury waiting periods are shorter than the roughly week-long governance process, which leaves intervention dependent on the Community Multisig, a separate group of signers. Mersin argues voters need an effective way to overrule treasury operators. The Compound Foundation counters that longer delays would impede operations and empower a concentrated voting position.

The timing limitation predates the current dispute. In its April security assessment, auditor Certora found that governance could not block or cancel individual escrow withdrawals, and that the treasury safeguard could reverse a pause. Certora rated the finding low severity; the customer response described reliance on the faster safeguard as an accepted trust model. The Foundation's original treasury framework likewise treated the Community Multisig's commitment to block disbursements during a governance reclaim proposal as an operational norm, not a hard contract requirement.

Who is behind the 1.75 million votes?

The voting position relies on dCOMP, an API3-built wrapper that separates borrowing collateral from the exercise of COMP voting rights. API3's documentation states that users can wrap COMP, pledge dCOMP as collateral on Morpho and borrow USDC while preserving the underlying COMP's voting power.

The wrapper's code specifies one-for-one wrapping, restricts deposits to whitelisted addresses and lets its owner change the recipient of the aggregated votes. Wrapping preserves votes; it does not multiply the number of COMP tokens carrying them.

Etherscan showed approximately 1.75 million COMP in the wrapper on Oct. 5. Its initial designated delegate, the address beginning 0x3B64, is the wallet that cast the 1.75-million-COMP vote for Proposal 612. Blockful's research attributes that voting position to Humpy.

Mersin has publicly acknowledged the relationship. "Humpy is delegating to me," he wrote in an earlier forum discussion. He defended dCOMP as a governance-enabled borrowing product and argued that preserving voting rights within financial strategies should not become objectionable because of who uses them.

In an Oct. 1 forum statement, the Foundation argued that extending delays would slow treasury operations precisely while it is tasked with accelerating Compound V4. It described the recent proposals as part of an allegedly malicious governance campaign associated with Humpy. That characterization is the Foundation's own, not an established finding about Proposal 612.

What happens if the vote passes?

The dispute follows Compound's 2024 settlement with Humpy over the goldCOMP proposal, which ended an alleged governance attack by agreeing to distribute 30% of reserves to COMP stakers.

Even if Proposal 612 passes, it would not immediately rewrite treasury mechanics. The proposal leaves the Community Multisig's power to veto governance proposals intact, along with existing payment streams' cancellation rules. And the Treasury Timelock's ten-day delay would itself require a second execution step after its existing two-day wait: the first proposal only schedules the change, and an authorized executor or a follow-up governance proposal must complete it.