KVORUM
compoundSource: Compound governor bravo · #109

Reserve Factor Decreases for 10 Assets

defeatedJun 18, 2022, 12:46 PM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Proposal to decrease reserve factors for 10 Compound assets based on Gauntlet's analysis showing the protocol has sufficient reserves ($42.87M) and annual growth ($3.86M) to cover potential losses. Decreases will redirect ~$1.53M annually from reserves to suppliers, improving capital efficiency while maintaining coverage for severe loss events.

Type
parameter change

Key changes

  • Decrease reserve factors for USDC, USDT, and TUSD from 7.5% to 3.75%(high)
  • Decrease reserve factors for 7 other assets by 500 basis points (e.g., ETH from 20% to 15%)(high)
  • Reduce annual reserve growth from $3.86M to $2.33M, reallocating $1.53M to suppliers(high)

Notable concerns

  • Proposal limited to 10 assets when Gauntlet initially recommended 17 total assets for reserve factor decreases
  • Protocol's one-week rolling average VaR for Black Thursday magnitude event is $0.30M, which is significantly lower than existing reserves
Contracts0x4ddc2d193948926d02f9b1fe9e1daa0718270ed50x39aa39c021dfbae8fac545936693ac917d5e75630xccf4429db6322d5c611ee964527d42e5d685dd6a0x5d3a536e4d6dbd6114cc1ead35777bab948e36430xf650c3d88d12db855b8bf7d11be6c55a4e07dcc90x12392f67bdf24fae0af363c24ac620a2f67dad860x6c8c6b02e7b2be14d4fa6022dfd6d75921d90e4e0xb3319f5d18bc0d84dd1b4825dcde5d5f7266d4070x35a18000230da775cac24873d00ff85bccded5500xface851a4921ce59e912d19329929ce6da6eb0c7
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

425 words

Reserve Factor Decreases for 10 Assets

Simple Summary

A proposal to adjust ten (10) parameters for ten (10) Compound assets.

Background

As planned in an earlier forum post, Gauntlet has updated its dynamic parameter methodology to include recommendations for the reserve factor, as well as our usual parameters. To outline our thinking behind this addition, we split lending parameter optimization into a two step process:

  • Balancing losses due to insolvency with capital efficiency
  • Balancing the tradeoff between increasing supplier APY and growing reserves to cover insolvency losses

We are now adding a layer to our existing simulation logic that allows us to reflect the second step of lending protocol risk management: building sufficient but not excessive reserves to absorb losses that do occur. Our model assumes the protocol would like to build reserves greater than insolvency losses by a small margin, and includes this as an optimization objective. As reserves are built and losses occur in the simulation, a higher setting for the reserve factor allows us to absorb more losses while maintaining reserve coverage, while a lower setting for the reserve factor would require losses to be managed more tightly.

Full proposal and forum discussion

Motivation and Specification

Recommendations:

We recommend decreasing reserve factors for USDC, USDT, and TUSD from 7.5% to 3.75%, and decreasing all other reserve factors by 500 bps (for example, decreasing ETH reserve factor from 20% to 15%). We previously proposed decreasing reserve factors for 17 total assets, but the maximum number of proposal changes is 10. As a result, we are recommending the 10 most impactful reserve factor decreases, based on expected annual reserves for each asset.

Reasoning:

The one-week rolling average VaR for Compound in a Black Thursday magnitude event is $0.30M.

The protocol has an existing reserve pool of $42.87M, broken down as follows:

The protocol is expected to build reserves at a $3.86M annual rate should the reserve factors remain unchanged, broken down as follows:

Since the existing pool and growth rate are more than sufficient to cover a very severe loss event, our analysis shows that the optimal level of reserve factors is well lower than they are currently. By implementing the recommended cuts, the protocol could reduce its estimated annual reserve growth rate from $3.86M to $2.33M, reallocating $1.53M of funds to suppliers and thus incentivizing more users to lock collateral in Compound.

By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos.

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent

The proposal describes 10 reserve-factor decreases: three stablecoins (USDC, USDT, TUSD) cut from 7.5% to 3.75%, and other assets cut by 500bps each, using ETH (20%→15%) as an example. The calldata contains exactly 10 _setReserveFactor calls. The target addresses for cETH, cUSDC, cUSDT, and cTUSD match well-known Compound cToken addresses, and their new values (15% for ETH, 3.75% for the three stablecoins) exactly match the description's stated targets. The remaining six actions set varying reserve factors (10%, 15%, 20% x4) consistent with a uniform 500bps reduction applied to differing starting reserve factors across assets, which the description explicitly anticipates ('decreasing all other reserve factors by 500 bps'). No extra actions, omitted actions, or mismatched targets/values were found. Because the calldata only shows resulting values (not prior values), full verification of the exact 500bps delta for the non-stablecoin assets isn't possible from calldata alone, but the pattern and named examples align precisely with the description, and no red flags (fund transfers, role changes, unrelated targets) are present.The proposal appears to faithfully implement what it describes.

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

04Actions

10 total
#0_setReserveFactor(uint256)chain 0x1
Target
0x4ddc…0ed5
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "150000000000000000"
}
Calldata
#1_setReserveFactor(uint256)chain 0x1
Target
0x39aa…7563
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "37500000000000000"
}
Calldata
#2_setReserveFactor(uint256)chain 0x1
Target
0xccf4…dd6a
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "150000000000000000"
}
Calldata
#3_setReserveFactor(uint256)chain 0x1
Target
0x5d3a…3643
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "100000000000000000"
}
Calldata
#4_setReserveFactor(uint256)chain 0x1
Target
0xf650…dcc9
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "37500000000000000"
}
Calldata
#5_setReserveFactor(uint256)chain 0x1
Target
0x1239…ad86
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "37500000000000000"
}
Calldata
#6_setReserveFactor(uint256)chain 0x1
Target
0x6c8c…0e4e
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "200000000000000000"
}
Calldata
#7_setReserveFactor(uint256)chain 0x1
Target
0xb331…d407
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "200000000000000000"
}
Calldata
#8_setReserveFactor(uint256)chain 0x1
Target
0x35a1…d550
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "200000000000000000"
}
Calldata
#9_setReserveFactor(uint256)chain 0x1
Target
0xface…b0c7
Value
0 wei
Function
_setReserveFactor(uint256)
Arguments
{
  "0": "200000000000000000"
}
Calldata

05Tally

Summed from votes

Voters341
VP participating524.9K
Outcome (current)Against
Current support21.4%

06Voters

341 total

No votes recorded yet.

07Forum

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

Arguments for

  • The protocol has accumulated more than sufficient reserves ($42.87M) to cover severe loss events (Black Thursday VaR of $0.30M), making current reserve factors unnecessarily high.— klinsuain, dvf
  • Decreasing reserve factors would reallocate approximately $1.53M annually to suppliers, increasing supplier APY and incentivizing more capital inflow to the protocol.— klinsuain, dvf
  • The protocol has effectively banked six years worth of reserves at current size, indicating reserve accumulation well exceeds prudent levels.— dvf
  • Reserve factor adjustments are low-risk parameter changes that only immediately affect supplier APYs and reserve growth, and can be easily reversed if conditions change.— klinsuain

Arguments against

  • Reducing reserves undermines the protocol's long-term revenue sustainability and ability to fund operations like Gauntlet services and OpenZeppelin ($1M quarterly) without relying on COMP token issuance.— Sirokko, blck
  • Most markets are currently over-supplied, so decreasing reserve factors to raise supply rates will not materially increase borrowing demand or user returns due to equilibrium dynamics.— Sirokko, rleshner
  • The protocol's reserve growth ($3.86M annually) does not adequately cover existing service costs, making further reductions imprudent before COMP tokens run out.— Sirokko, blck
  • VAR-based risk assessment does not adequately account for long-tail market events like severe collateral price crashes, which could invalidate reserve sufficiency assumptions.— RogerS
  • Reserve reallocation from over-reserved assets (BAT, ZRX) to under-reserved ones (USDC, ETH) would be a better approach than uniform reserve factor cuts.— rleshner

Unresolved concerns

  • What happens to reserve growth assumptions if collateral asset prices fall significantly (e.g., 50% ETH decline), and how sensitive are the $3.86M annual growth projections to market conditions?— RogerS, klinsuain
  • How will the protocol sustain funding for services like Gauntlet and OpenZeppelin once COMP tokens are depleted if reserves continue to decline?— Sirokko, blck
  • Should the protocol instead reallocate reserves between markets based on borrowing-to-reserve ratios rather than implementing uniform reserve factor cuts?— rleshner

Notable participants

  • klinsuainGauntlet representative who proposed the reserve factor methodology and recommendations, defending the analysis and answering technical questions.
  • SirokkoLeading opponent who argued the proposal undermines protocol revenue sustainability and questioned whether reserve decreases address over-supplied markets.
  • rleshnerCore contributor who agreed with concerns, voted against the proposal, and suggested alternative reserve management approaches like inter-market reallocation.
  • dvfEarly supporter who argued reserves are excessive relative to protocol size and questioned how reserve factors would scale with growth.
  • blckOpponent who highlighted that protocol expenses already exceed reserve growth, making further reductions counterproductive.
  • RogerSSkeptic who questioned the robustness of reserve growth projections under severe market downturns and VAR limitations.
  • inkymazeGauntlet team member who acknowledged feedback and offered to facilitate reversal of reductions if needed.
  • pauljleiCoordinator who announced the on-chain vote timeline and later indicated Gauntlet would return with an updated proposal.
  • jake.aujusGauntlet team member who provided technical update on proposal structure and vote execution.
  • ClairvoyantLabsCritic who questioned Gauntlet's utility and suggested canceling their engagement could save protocol resources.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗