WOOF! <> Compound 2025
01Summary
Renew WOOF!'s 12-month engagement with Compound to support core protocol developments including Compound v4, staked COMP, and partial liquidations. Compensation: 53,011 COMP (valued at $2,000,000 USD) streamed over 1 year via a custom audited solution.
- Type
- treasury allocation
- Funding
- $2000000
Key changes
- Grant 53,011 COMP tokens to WOOF! streaming address for 12-month engagement(high)
- Implement second-by-second COMP streaming with USDC valuation via Chainlink price feed(high)
- Establish $2,000,000 USD claiming cap with 0.5% slippage tolerance(high)
- Enable community-executed claims if last claim exceeds 7 days and early stream cancellation via governance vote(medium)
- Allow unclaimed COMP return to Comptroller after 1-year stream plus 10-day grace period(medium)
Notable concerns
- WOOF! can withdraw vested funds at any time without restrictions
- Slippage tolerance of 0.5% may result in COMP claims below intended $2,000,000 value
- Community relies on voluntary claim execution if WOOF! does not claim for 7+ days
- Services governed by updated Terms of Service as of November 29, 2024
Generated by Kvorum
02Description
WOOF! <> Compound 2025
Background
Since 2023, WOOF! has worked with Compound to support the new and ongoing developments.
Full details of the proposal can be found here.
Proposal
A proposal to renew WOOF!’s 12-month engagement with Compound to support core Compound Protocol developments, addressing the evolving needs of the community, including Compound v4, staked COMP, partial liquidations, and more, while also maintaining and supporting the existing infrastructure.
Compensation Structure
The service fee structure will be a fixed annual fee of 2,000,000 USD using the COMP spot price.
COMP will be streamed via a custom solution developed by WOOF! and audited by OpenZeppelin.
Specification:
-
Allocation: 53,011 COMP
-
Streaming Duration: 1 year (continuously, second-by-second distribution)
-
Distribution Currency: COMP, valued in USDC via Chainlink’s COMP/USDC price feed at the moment of claim.
-
Claiming Cap: 2,000,000 USDC.
-
Slippage Tolerance: 0.5% applied at the time of claim.
-
Claim Safeguard: To protect the DAO from unfavorable claim conditions, any address may execute a claim on behalf of the stream if the last claim occurred more than 7 days ago.
-
Anyone can return unclaimed COMP to the Comptroller after the end of the stream, plus a 10-day grace period.
-
The stream can be canceled early via an on-chain governance vote.
-
WOOF! will be able to withdraw the vested funds at any time.
More details can be found in the forum post.
By approving this proposal, you agree that any services provided by WOOF! shall be governed by the Terms of Service that were updated as of November 29, 2024.
03Mismatch analysis
The proposal describes a fixed annual compensation of 53,011 COMP streamed via a custom contract audited by OpenZeppelin, with the stream to be initialized for continuous distribution. The calldata shows exactly two actions: (1) Comptroller._grantComp granting 53,011 COMP (53011e18 wei) to a specific address, matching the stated allocation amount precisely, and (2) an initialize() call on that same address, which aligns with standing up the streaming contract as described. There are no numeric mismatches (53,011 COMP matches exactly), no target mismatches (both actions point to the same recipient/stream contract), and no omitted or extra actions relative to what the description claims. The initialize() call is a routine bookkeeping step consistent with deploying/activating the described streaming mechanism and does not represent an undisclosed action. Overall the description and calldata are well aligned with high confidence.
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _grantComp(address,uint256)
- Arguments
{ "amount": "53011000000000000000000", "recipient": "0xF088339DD8e79819A41aDD5FFB75d9F245AfaAb1" }- Calldata
- Target
- 0xf088…aab1
- Value
- 0 wei
- Function
- initialize()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- 🐶 WOOF! <> Compound 2025 ↗discourse · high confidence
Arguments for
- WOOF has demonstrated exceptional technical expertise and delivery track record over 18 months, having pushed 80+ on-chain proposals, deployed 17 new markets across 9 chains, and delivered key products like Rewards v2, Migrator, and Comet Wrapper.— PGov, torrey, AranaDigital, bryancolligan, jbass-oz
- Compound lacks a dedicated core development team since Compound Labs departed, causing it to lose market share to faster-iterating competitors; WOOF can fill this critical gap and maintain protocol competitiveness.— woof, Avantgarde, AranaDigital
- The 2M USDC ask is proportionate to scope and significantly cheaper (2-3x lower) than comparable DAO teams like BGD Labs at AAVE (~6M) and Euler (~4.5M) while delivering similar or greater output.— woof, Avantgarde
- The custom streaming contract provides the DAO with full control over COMP distribution, transparent vendor payments, and the ability to cancel the stream early via governance vote if unsatisfied.— woof, jbass-oz
- A bundled 12-month mandate enables agile responsiveness to emerging market opportunities like partnerships and integrations that competitors can otherwise capture first.— woof, bryancolligan
- WOOF's open-source front-end and SDK development, documentation updates, and support infrastructure strengthen Compound's decentralization and accessibility for partners and contributors.— woof, Avantgarde
- The Compound Foundation has signaled alignment and expectation to collaborate closely with WOOF on product and protocol evolution once the Foundation is operational.— Compound_Foundation
Arguments against
- A 12-month bundled mandate conflates maintenance and long-horizon R&D without clear specifications or checkpoints, making budgeting and accountability unclear compared to separate, milestone-based proposals.— Gauntlet
- The proposed Compound Foundation and WOOF's proposal have overlapping scopes on product roadmap, protocol improvements, and strategic growth, creating potential redundancy and unclear ownership of responsibilities.— Gauntlet
- Given the Foundation's intended role as centralized leadership for strategy and development coordination, protocol-level R&D and strategic planning should fall under the Foundation's purview rather than WOOF's, reducing scope conflicts.— Gauntlet
- A lighter engagement (2-3 months) would be more prudent given Compound's current crossroads, allowing time to reevaluate after Sandbox delivery before committing to a full-year, full-scope mandate.— cmrn
Unresolved concerns
- How will WOOF prioritize among the extensive list of potential development initiatives, and what would a concrete 12-month roadmap with specific timelines and deliverables look like?— Avantgarde
- What specific metrics or KPIs will be used to evaluate WOOF's success after 12 months, beyond track record and community feedback?— PGov
- Given that the Compound Foundation is still six months away, how will responsibilities and authority be clarified to prevent conflicts between WOOF and the Foundation once it launches?— Gauntlet, bryancolligan
- Is WOOF operating within the scope of the separate Compound Foundation proposal, or are they conflicting governance structures that need clarification?— Onedayimay
Notable participants
- woofProposal author and lead of WOOF team; provided detailed retrospective, mandate breakdown, streaming solution, and responses to community feedback.
- GauntletProvided critical structural feedback questioning the bundled mandate approach and recommending separate maintenance and R&D proposals to improve accountability.
- PGovPraised WOOF's helpfulness and asked clarifying questions about success metrics, prior funding scope, and Sandbox updates.
- cmrnSuggested a lighter 2-3 month engagement instead of full 12-month mandate to allow reevaluation after Sandbox delivery.
- AvantgardeStrongly supported the proposal, acknowledged WOOF's track record, and asked about prioritization and roadmap details for labor-intensive projects.
- Compound_FoundationSignaled initial alignment with WOOF's proposal and intent to collaborate closely on product and protocol evolution.
- AranaDigitalAttested to WOOF's delivery quality, emphasized importance of progress tracking, and supported the proposal with conditions on KPI evaluation.
- torreyAffirmed WOOF as the most knowledgeable team on Compound v3 outside original Labs and supported continued operational funding.
- jbass-ozOpenZeppelin representative who reviewed and approved the Streamer contract, noting only superficial differences from audited version.
- bryancolliganPraised WOOF's responsiveness, professionalism, and consistent delivery over the year, noting the backlog exists while Foundation ramps up.
Generated by Kvorum
08Similar proposals
- compoundcanceledOpenZeppelin Security Partnership - Annual Renewal 202580%
- compoundexecutedOpenZeppelin Security Partnership - Annual Renewal 202579%
- compoundexecutedCompound Sandbox: Development Proposal78%
- compoundexecutedCompound <> Gauntlet Year 5 Partnership77%
- compoundexecutedGauntlet <> Compound Renewal 202370%
- compoundexecutedGauntlet <> Compound Renewal 202470%
- compoundexecutedOpenZeppelin Security Partnership - Annual Renewal 202469%
- compoundexecutedFinalize Security Service Provider Engagement (2025)69%
- compoundexecutedGauntlet <> Compound Incentive Optimization69%
- compoundexecutedOpenZeppelin Continuous Audit & Security Services Proposal67%