Note: This feedback was written before the proposal moved on-chain; it’s meant to sharpen scope and budget to support a constructive discussion.
The proposal bundles two distinct tracks, protocol maintenance and long-horizon R&D, into a single 12-month mandate. This conflation makes budgeting and accountability unclear.
The DAO would be better served by first approving a lean, SLA-driven maintenance contract and then evaluating larger initiatives (e.g., Staked COMP, partial liquidations, Kill Switch, Cross-chain Lending, OEV) through separate, milestone-based proposals once they are scoped and specified.
Governance & Accountability:
A 12-month bundled mandate, including maintenance and innovation, commits the DAO to conceptual workstreams without clear specifications or review checkpoints. Splitting the scope allows the community to weigh in on technical specs, provide feedback, and assess economic tradeoffs prior to committing funds.
Foundation Alignment:
The recently proposed Compound Foundation is intended to lead protocol strategy, coordinate service providers, execute product direction, and represent Compound externally. This significantly overlaps with responsibilities outlined in WOOF!’s forum post.
Both proposals describe ownership of:
- Product roadmap and protocol improvements (e.g., Staked COMP, Kill Switch, Cross-chain Lending)
- Strategic growth and integrations
- Maintenance of front-end infrastructure
This dual structure raises two concerns:
- Redundant scopes: Both teams seek DAO funding to lead strategy, development, and coordination.
- Unclear authority: Without clarified ownership, accountability for execution becomes ambiguous.
Given the Foundation’s role as a centralized point of leadership and coordination, protocol-level R&D and strategic planning should likely fall under its purview, with service providers like WOOF executing clearly scoped workstreams.
Recommendation
- Focus this proposal on core protocol maintenance: chain deployments, collateral listings, documentation, and other V3 responsibilities.
- Defer product roadmap, strategy, and R&D initiatives to the Compound Foundation to prevent conflicting mandates.
- Return with standalone proposals for R&D initiatives once initial specifications and milestone-based budgets are well defined.
We support continued protocol development and appreciate WOOF!’s track record. With a clearer scope and budget structure, this proposal could form the basis of a strong, sustainable service relationship with the DAO.