KVORUM
compoundSource: Compound governor bravo · #72

Risk Parameter Updates for WBTC, UNI, and COMP

executedDec 6, 2021, 05:44 AM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Batch update of collateral factors for WBTC, UNI, and COMP to align with community-chosen Moderate risk level. Changes increase Value at Risk slightly but enable substantially higher borrow usage through dynamic risk parameter adjustments.

Type
parameter change

Key changes

  • Set WBTC collateral factor to 65% (0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4)(medium)
  • Set UNI collateral factor to 70% (0x35A18000230DA775CAc24873d00Ff85BccdeD550)(medium)
  • Set COMP collateral factor to 70% (0xC11b1268C1A384e55C48c2391d8d480264A3A7F4)(medium)

Notable concerns

  • Slight increase in Value at Risk (VaR) from parameter adjustments
  • Parameters differ from original risk level consensus due to changing market conditions
Contracts0x3d9819210a31b4961b30ef54be2aed79b9c9cd3b0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e40x35A18000230DA775CAc24873d00Ff85BccdeD5500xC11b1268C1A384e55C48c2391d8d480264A3A7F4
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

168 words

Risk Parameter Updates for WBTC, UNI, and COMP

Simple Summary

A proposal to adjust three (3) total parameters across three (3) Compound assets.

Background

This proposal is a batch update of risk parameters to align with the Moderate risk level chosen by the Compound community. These parameter updates are the fourth of Gauntlet's regular parameter recommendations as part of Dynamic Risk Parameters.

Full proposal and forum discussion

Motivation and Specification

This set of parameter updates seeks to level set assets to a Moderate risk level of the protocol while making risk trade-offs between specific assets. Note that some are different from the original risk level consensus check as market conditions have changed.

Dashboard

Gauntlet has launched the Compound Risk Dashboard. The community should use the Dashboard to better understand the updated parameter suggestions and general market risk in Compound.

As shown on our dashboard, these changes will slightly increase Value at Risk, but the corresponding increase in borrow usage is substantial.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The description states this is a batch update touching three parameters across three Compound assets (WBTC, UNI, COMP), consistent with a Gauntlet risk-parameter recommendation. The decoded calldata contains exactly three _setCollateralFactor calls against the Comptroller, each targeting a distinct cToken address and setting a new collateral factor (65%, 70%, 70%). This matches the claimed count of '3 parameters across 3 assets' (one parameter change per asset), and collateral factor is the standard lever Gauntlet adjusts in these routine proposals. The description does not include the specific numeric targets in the text itself (they are shown only in a linked image), so I cannot independently verify that 65%/70%/70% correspond exactly to the intended WBTC/UNI/COMP values or that the addresses map correctly to those tickers — this limits confidence to medium rather than high. However, nothing in the calldata contradicts the description: there are no unexpected extra actions, no transfers of funds, and no unrelated targets. Given the structural match (3 assets, 3 single-parameter collateral-factor updates) and the routine nature of this Gauntlet parameter proposal, I assess this as consistent with only the caveat that the exact numeric mapping to specific assets could not be confirmed from text alone.

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

04Actions

3 total
#0_setCollateralFactor(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCollateralFactor(address,uint256)
Arguments
{
  "0": "0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4",
  "1": "650000000000000000"
}
Calldata
#1_setCollateralFactor(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCollateralFactor(address,uint256)
Arguments
{
  "0": "0x35A18000230DA775CAc24873d00Ff85BccdeD550",
  "1": "700000000000000000"
}
Calldata
#2_setCollateralFactor(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCollateralFactor(address,uint256)
Arguments
{
  "0": "0xC11b1268C1A384e55C48c2391d8d480264A3A7F4",
  "1": "700000000000000000"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

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

Arguments for

  • Parameter updates align with the community-chosen Moderate risk level and represent Gauntlet's fourth regular recommendation under the Dynamic Risk Parameters framework.— pauljlei
  • The changes will substantially increase borrow usage on the protocol while only slightly increasing Value at Risk.— pauljlei
  • The $413k increase in reserves provides a safety buffer against potential risks from the collateral factor increases.— pauljlei

Arguments against

  • A typo in the WBTC implementation that updated only the legacy pool instead of the active WBTC collateral factor indicates quality control issues in Gauntlet's process and raises concerns about future mistakes that could compromise user funds.— eggbagels

Unresolved concerns

  • Whether Gauntlet has established adequate processes to prevent similar implementation bugs or typos in future parameter update proposals.— eggbagels

Notable participants

  • pauljleiProposer of the risk parameter updates on behalf of Gauntlet.
  • eggbagelsCommunity member who identified a critical implementation bug in the WBTC collateral factor update and raised quality control concerns.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗