KVORUM
compoundSource: Compound governor oz · #536

Authorization of Treasury Management Use of Compound v2 Reserves

executedFeb 17, 2026, 02:21 PM UTCby3F0x3fb1…4c8a

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal authorizes the Compound Foundation to establish a treasury management framework for 8.42 million DAI from deprecated Compound v2 reserves. The Foundation can deploy these idle reserves to support protocol operations and maintain sufficient COMP for reward distribution and governance functions, with quarterly reporting and oversight via a 4-of-6 multisig wallet.

Type
treasury allocation
Funding
$8.42 million DAI (approximately)

Key changes

  • Transfer 8.42 million DAI from Compound v2 reserves to Foundation-administered multisig wallet (0x0F5100684d0530A8321976B376a3196eb481c7bD)(high)
  • Establish governance framework enabling Foundation to deploy v2-related DAI reserves for protocol operations and maintaining COMP liquidity for reward distribution and governance execution(high)
  • Create 4-of-6 multisig with signers from Compound Foundation, Governance Working Group, and Security Service Provider for oversight and checks-and-balances(high)

Notable concerns

  • Authorization is narrowly scoped to v2 DAI reserves only; no other treasury assets included
  • Proposal does not prescribe specific transactions or execution strategies; future actions subject to quarterly reporting
  • Foundation may engage Gauntlet or other third parties for implementation support
  • Authorization explicitly prohibits use of v2 reserves for Foundation overhead, personnel costs, or existing vendor relationships
Contracts0x5d3a536e4d6dbd6114cc1ead35777bab948e36430x6b175474e89094c44da98b954eedeac495271d0f
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

925 words

Authorization of Treasury Management Use of Compound v2 Reserves

Summary

This proposal seeks governance approval to establish a limited framework for stewarding a defined portion of protocol reserves associated with Compound v2 following its deprecation and wind-down. With v2 markets now inactive, these reserves are no longer required for liquidation backstopping or other v2 risk management purposes and are currently sitting idle. This proposal authorizes the Compound Foundation, acting via qualified service providers and subject to existing governance oversight, to manage a designated allocation of these v2 reserves in support of the Compound protocol and DAO.

Specifically, this authorization enables the Compound Foundation to:

  • Establish and operate a treasury management framework for specific assets accessible due to the Compound v2 deprecation.
  • Utilize the assigned v2-related reserves in a controlled and accountable manner to support ongoing protocol operations and make the assigned capital productive.
  • Implement these activities in a manner consistent with prudent stewardship, market sensitivity, and the intent of prior governance decisions.

Importantly:

  • No specific transactions, execution strategies, or market actions are prescribed by this proposal but will be included in future reporting.
  • This proposal’s authorization is narrowly scoped to DAI from v2-related reserves.
  • The DAO’s existing treasury strategies remain unchanged.
  • These funds are entirely DAO-owned and will not be used to fund Foundation-specific operations.

Background and Governance Context

Compound governance previously approved the deprecation of Compound v2 markets pursuant to the Compound v2 Deprecation Proposal, which was passed by an on-chain vote.

That proposal included, among other measures:

  • Pausing new borrows and mints across v2 markets while allowing withdrawals, repayments, and liquidations to continue.
  • Increasing reserve factors across v2 markets to 100%.

As a consequence of this deprecation, v2 markets no longer require reserves to perform their original risk-management function. While residual user positions continue to close over time, the associated protocol reserves are no longer actively deployed for market operations and instead remain latent. These balances persist as a byproduct of the deprecation process rather than as part of an ongoing market or treasury strategy.

To date, governance has not established a specific framework for how these v2-related reserves should be stewarded once their original purpose ceased. This proposal provides the necessary governance context and authorization to responsibly manage a defined portion of those reserves, without altering the DAO’s broader treasury mandate or existing strategies.

Purpose of This Proposal

The goal of this proposal is to enable the Foundation to establish a treasury management framework for the responsible stewardship of assets that have become available as a result of the Compound v2 deprecation and wind-down, and to ensure these assets are put to efficient and deliberate use in support of specific protocol operations rather than remaining idle.

For instance, COMP held by the Comptroller continues to be distributed through reward claims and is also required for certain governance actions. Taken together, these dynamics have resulted in a mismatch between available COMP balances in the Comptroller and the operational requirements of the protocol. This represents a potential challenge that the Foundation may address by way of the new treasury management framework.

This proposal, however, does not establish an explicit treasury management program from the outset, nor does it alter existing treasury strategies like Avantgarde-managed covered calls. Instead, it enables the Foundation, via appropriate service providers, to steward latent reserves in a manner prudent for addressing important protocol needs.

Treasury Management Facilitation and Implementation

If approved, the Foundation will be:

  • Authorised to facilitate treasury management activities, via qualified service providers, using only the Compound v2 DAI reserves, which currently total approximately 8.42 million DAI.
  • Allowed to maintain sufficient COMP availability for protocol components that depend on it, such as reward distribution and other forms of governance execution.

Any such facilitation or implementation will be conducted in accordance with existing governance controls, reporting expectations, and fiduciary standards. The Foundation may engage Gauntlet or other third parties as an implementation partner to support analysis, execution, and operational decision-making related to such treasury management activities.

Scope of Authorisation

  • Eligible Assets: This authorization applies solely to the DAI reserves associated with deprecated Compound v2 markets, which currently total approximately 8.42 million DAI. No other DAO treasury assets, reserve balances, or protocol revenues are included within the scope of this authorization.
  • Permitted Objectives: assets within scope may be managed or deployed exclusively to support protocol operations and governance continuity, including maintaining sufficient COMP availability for components that rely on it, such as reward distribution and governance execution. The authorization does not extend to discretionary trading/speculative activity or deployment of funds to non-essential operations.
  • Facilitation and Oversight: The Foundation may engage Gauntlet or other qualified third parties for analysis or implementation support where appropriate. Reporting will be conducted retrospectively on a quarterly basis.
  • Isolated Mandate: This authorization does not modify existing treasury strategies. This authorization does not permit the use of v2 deprecation reserves to fund Foundation overhead, personnel costs, or expenses related to any existing vendor or service-provider relationships. Such obligations remain governed by separate, explicitly approved arrangements.

Proposed Action

Upon approval, all 8.42 million DAI from v2 reserves will be transferred to a newly designated, Foundation-administered multisig wallet established solely for the purposes of this authorization. The multisig will be configured with an elevated security threshold (4-of-6) to ensure appropriate checks and balances while preserving operational flexibility. Signers will be drawn from the Compound Foundation, the Governance Working Group (CGWG) and the Security Service Provider (SSP) team, with two representatives from each group.

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent

The proposal describes a two-step action: (1) pull ~8.42 million DAI in idle reserves out of the deprecated Compound v2 DAI market, and (2) transfer that DAI to a newly created Foundation-administered 4-of-6 multisig for treasury management. The calldata matches this precisely: action 0 calls _reduceReserves on the cDAI v2 market contract for exactly 8,420,000 DAI (8420000000000000000000000 wei, 18 decimals), and action 1 transfers the identical amount of DAI to a single destination address. The dollar figure in the calldata (8.42M DAI) matches the prose's stated figure exactly after unit conversion, and the sequence of reduce-then-transfer aligns with the narrative of moving reserves to a new multisig. There is no way from the calldata alone to independently verify that the destination address is indeed the described 4-of-6 Foundation/CGWG/SSP multisig, but this is expected — governance calldata does not encode multisig ownership metadata, and there is no evidence contradicting the description (e.g., no split transfers, no unrelated targets, no COMP-related transfers despite COMP being discussed narratively as context only, not as an authorized action). No amounts, targets, or actions in the calldata contradict or exceed what the description claims, and no significant on-chain action is omitted from the narrative. Given the tight numerical match and consistent action sequence, I assess this proposal as consistent with high confidence.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

2 total
#0_reduceReserves(uint256)chain 0x1
Target
0x5d3a…3643
Value
0 wei
Function
_reduceReserves(uint256)
Arguments
{
  "reduceAmount": "8420000000000000000000000"
}
Calldata
#1transfer(address,uint256)chain 0x1
Target
0x6b17…1d0f
Value
0 wei
Function
transfer(address,uint256)
Arguments
{
  "amount": "8420000000000000000000000",
  "address": "0x0F5100684d0530A8321976B376a3196eb481c7bD"
}
Calldata

05Tally

Summed from votes

Voters60
VP participating1.7M
Outcome (current)For
Current support91.9%

06Voters

60 total
Filter:
VoterChoice% of totalRationale
B00xb06d…ae3dFor428.3K25.13%—9mo ago
B90xb933…8dd1For243.5K14.29%—9mo ago
3F0x3fb1…4c8aFor104.8K6.15%—9mo ago
810x8169…9806For101K5.93%—9mo ago
360x36cc…ffc6Against87.6K5.14%—9mo ago
660x66cd…65f9For80K4.69%—9mo ago
B30xb356…c826For60.1K3.53%—9mo ago
B40xb49f…7948For60K3.52%—9mo ago
050x0579…ca09For60K3.52%—9mo ago
170x1729…b879For60K3.52%—9mo ago
B70xb792…89d7For60K3.52%—9mo ago
D20xd2a7…5a0cFor60K3.52%—9mo ago
8D0x8d07…a265For55K3.23%—9mo ago
070x0703…961bFor51.7K3.04%—9mo ago
2B0x2b38…bf33For50.1K2.94%—9mo ago
4F0x4f89…fd3cAgainst50K2.93%—9mo ago
680x683a…6c02For35.6K2.09%—9mo ago
130x13bd…8548For30K1.76%—9mo ago
D70xd7e7…08beFor8K0.47%—9mo ago
TEtennisbowling.eth0xc3aa…f546For5K0.29%—9mo ago
860x862e…5267For5K0.29%—9mo ago
CB0xcbf0…94a3For4.3K0.25%—9mo ago
5C0x5c04…dc62For2.7K0.16%—9mo ago
CE0xce8a…8ca3For6700.04%—9mo ago
1F0x1f3d…0591For440.70.03%—9mo ago
BE0xbe1d…c953For2310.01%—9mo ago
C50xc554…7759For11.20.00%—9mo ago
010x0151…c3b9For1.10.00%—9mo ago
9F0x9f77…2768For10.00%—9mo ago
880x88f6…0ec0For00.00%—9mo ago
B30xb344…11f8For00.00%—9mo ago
DD0xdd68…d51bFor00.00%—9mo ago
F10xf1d8…e355For00.00%—9mo ago
8C0x8cbe…0910For00.00%—9mo ago
030x039d…837aFor00.00%—9mo ago
B20xb209…ad67For00.00%—9mo ago
E10xe197…1904For00.00%—9mo ago
370x3794…dd07For00.00%—9mo ago
0B0x0b36…8563For00.00%—9mo ago
090x0939…3cd5For00.00%—9mo ago
030x036f…4714For00.00%—9mo ago
3B0x3ba3…333dFor00.00%—9mo ago
640x6460…2493For00.00%—9mo ago
460x4689…7a88For00.00%—9mo ago
150x1518…8637For00.00%—9mo ago
970x97f4…90caFor00.00%—9mo ago
A30xa3ec…5430For00.00%—9mo ago
770x77b1…d376For00.00%—9mo ago
070x072f…9fc5For00.00%—9mo ago
300x301e…5e40For00.00%—9mo ago
Showing 50

07Forum

AIForum synthesis by Kvorumclaude-haiku-4-5
sentiment · favorablethread · constructive

Arguments for

  • V2's pooled-collateral model creates systemic risk through cross-asset contagion and introduces unnecessary complexity compared to V3's proven production design.— Gauntlet
  • V2's broad parameter surface requires continual monitoring and increases misconfiguration risk, expanding the protocol's attack surface.— Gauntlet
  • V2 has experienced significant usage decline with the majority of activity shifted to V3, making continued maintenance of two versions inefficient.— Gauntlet
  • The deprecation plan is secure and does not include major protocol changes, while meaningfully reducing attack surface and complexity.— ioannis_csec
  • V2's design is less gas-efficient and more complex for external integrations compared to V3.— Gauntlet

Arguments against

None surfaced.

Notable participants

  • GauntletProposal author who introduced the V2 deprecation plan, timeline, and managed the voting process.
  • ioannis_csecSecurity provider expressing explicit support for the deprecation plan on behalf of SSPs.
  • CataUser requesting technical guidance on migrating positions from V2 to V3.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗