KVORUM
compoundSource: Compound governor bravo · #388

[Gauntlet] - Cap recommendations (01/21/25)

executedJan 26, 2025, 02:14 PM UTCby680x683a…6c02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Gauntlet recommends increasing supply caps for two assets across Compound V3 Comets: cbBTC cap in USDT Comet from 500 to 1,000, and tBTC cap in USDC Comet from 285 to 570. These changes aim to improve capital efficiency.

Type
parameter change

Key changes

  • Increase Ethereum V3 USDT Comet's cbBTC Supply Cap from 500 to 1,000(medium)
  • Increase Ethereum V3 USDC Comet's tBTC Supply Cap from 285 to 570(medium)
Contracts0xc3d688B66703497DAA19211EEdff47f25384cdc30x3Afdc9BCA9213A35503b077a6072F3D0d5AB08400x316f9708bb98af7da9c68c1c3b5e79039cd336e30x1ec63b5883c3481134fd50d5daebc83ecd2e8779
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

127 words

[Gauntlet] - Cap recommendations (01/21/25)

Summary

Gauntlet recommends the following risk recommendations to the protocol:

  • Increase Ethereum V3 USDT Comet’s cbBTC Supply Cap from 500 to 1,000.
  • Increase Ethereum V3 USDC Comet’s tBTC Supply Cap from 285 to 570.

Motivation

This recommendation aims to increase supply caps for various assets across multiple Comets. Gauntlet recommends to increase supply caps to increase capital efficiency within the Comets.

Full proposal and forum discussions can be found in the following posts.

Specification

The proposal updates the parameters by using the respective methods on the Configurator.

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

Verified both supply cap changes described in the proposal against the decoded calldata. Action 0 sets tBTC supply cap on the mainnet USDC Comet (0xc3d688...) to 570e18, matching '285 to 570' (tBTC has 18 decimals). Action 2 sets cbBTC supply cap on the mainnet USDT Comet (0x3Afdc9...) to 100,000,000,000 (1e11), which equals 1000 cbBTC given its 8 decimals, matching '500 to 1,000'. Both asset and comet addresses correspond to the tokens/markets named in the description (tBTC, cbBTC, USDC Comet, USDT Comet). Actions 1 and 3 are deployAndUpgradeTo calls to the Comet proxy factory — this is the routine, standard mechanism used to push Configurator parameter changes live and is not something a description of this type would be expected to itemize separately. No value, target, or magnitude mismatches were found, and no actions in the calldata are unaccounted for by the description's stated intent (two supply cap increases). Overall the description accurately and completely represents the on-chain actions.

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

04Actions

4 total
#0updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "0": "0xc3d688B66703497DAA19211EEdff47f25384cdc3",
  "1": "0x18084fbA666a33d37592fA2633fD49a74DD93a88",
  "2": "570000000000000000000"
}
Calldata
#1deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "0": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3",
  "1": "0xc3d688B66703497DAA19211EEdff47f25384cdc3"
}
Calldata
#2updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "0": "0x3Afdc9BCA9213A35503b077a6072F3D0d5AB0840",
  "1": "0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf",
  "2": "100000000000"
}
Calldata
#3deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "0": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3",
  "1": "0x3Afdc9BCA9213A35503b077a6072F3D0d5AB0840"
}
Calldata

05Tally

Summed from votes

Voters30
VP participating501.1K
Outcome (current)For
Current support100%

06Voters

30 total

No votes recorded yet.

07Forum

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

Arguments for

  • Supply cap increases are justified by high utilization rates (75%+) on various assets across chains, indicating market demand and the need to prevent caps from constraining legitimate user activity.— Gauntlet
  • Liquidation analysis shows acceptable slippage levels relative to liquidation penalties when caps are increased, indicating that larger caps can be safely accommodated without excessive risk.— Gauntlet
  • Top suppliers maintain strong health factors (often >1.4 to >4), demonstrating that large position holders are well-collateralized and pose low liquidation risk even at higher caps.— Gauntlet
  • Exchange rate oracles enable safer cap increases for assets like ezETH, wstETH, and weETH because liquidation pathways are constrained, reducing systemic risk from large caps.— Gauntlet
  • Asset supplies are growing and circulating supply on various chains supports higher cap levels relative to current utilization, allowing protocol to accommodate organic growth.— Gauntlet

Arguments against

None surfaced.

Unresolved concerns

  • sFRAX supply cap was increased since 12/9 but utilization data only shows through 12/8, leaving unclear whether the additional increase to 20M was justified by actual demand.— Tane
  • Top supplier data shown in images does not match the supplied amounts, raising questions about whether other large suppliers exist that should be displayed for transparency.— Tane
  • Top supplier addresses should be provided in text format rather than images for accessibility and to enable community verification of supplier identities and positions.— Tane

Notable participants

  • GauntletPrimary proposer issuing repeated supply cap recommendations backed by utilization data, slippage analysis, and top supplier health metrics.
  • TaneCommunity member raising questions about data currency, completeness of supplier disclosure, and format of supplier information.
  • dmitriywoofsoftwareCommunity participant who supported and accelerated one proposal to push it on-chain.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗