KVORUM
compoundSource: Compound governor bravo · #355

[Gauntlet] Supply Cap Recommendations - Part 1 (10/24)

executedNov 2, 2024, 04:00 PM UTCby4D0x4d80…ef4b

01Summary

AISummary by Kvorumclaude-haiku-4-5

Gauntlet recommends increasing supply caps for weETH and ezETH across five Comet instances on Optimism, Arbitrum, and Base to improve capital efficiency. Specific increases include: Optimism V3 WETH weETH (400→600), Arbitrum USDC ezETH (500→1,400), Arbitrum V3 WETH ezETH (6,400→10,240), Base V3 WETH ezETH (2,000→3,200), and Optimism V3 WETH ezETH (2,400→3,200).

Type
parameter change

Key changes

  • Increase Optimism V3 WETH Comet weETH supply cap from 400 to 600(medium)
  • Increase Arbitrum USDC Comet ezETH supply cap from 500 to 1,400(high)
  • Increase Arbitrum V3 WETH Comet ezETH supply cap from 6,400 to 10,240(high)
  • Increase Base V3 WETH Comet ezETH supply cap from 2,000 to 3,200(medium)
  • Increase Optimism V3 WETH Comet ezETH supply cap from 2,400 to 3,200(medium)
Contracts0xe36a30d249f7761327fd973001a32010b521b6fd0x2416092f143378750bb29b79ed961ab195cceea50x5a7facb970d094b6c7ff1df0ea68d99e6e73cbff0x46e6b214b524310239732d51387075e0e70970bf
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

173 words

[Gauntlet] Supply Cap Recommendations - Part 1 (10/24)

Summary

Gauntlet recommends the following risk recommendations to the protocol:

  • Increase Optimism V3 WETH Comet’s weETH Supply Cap from 400 to 600.
  • Increase Arbitrum USDC Comet's ezETH supply cap from 500 to 1,400
  • Increase Arbitrum V3 WETH Comet’s ezETH Supply Cap from 6400 to 10240.
  • Increase Base V3 WETH Comet’s ezETH Supply Cap from 2000 to 3,200.
  • Increase Optimism V3 WETH Comet's ezETH supply cap from 2,400 to 3,200

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 October 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 Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

3 total
#0sendMessage(address,bytes,uint32)chain 0x1
Target
0x25ac…5fa1
Value
0 wei
Function
sendMessage(address,bytes,uint32)
Arguments
{
  "0": "0xC3a73A70d1577CD5B02da0bA91C0Afc8fA434DAF",
  "1": "0x0000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001800000000000000000000000000000000000000000000000000000000000000320000000000000000000000000000000000000000000000000000000000000000300000000000000000000000084e93ec6170ed630f5ebd89a1aae72d4f63f271300000000000000000000000084e93ec6170ed630f5ebd89a1aae72d4f63f27130000000000000000000000003c30b5a5a04656565686f800481580ac4e7ed17800000000000000000000000000000000000000000000000000000000000000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e743132382900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e74313238290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000060000000000000000000000000e36a30d249f7761327fd973001a32010b521b6fd0000000000000000000000002416092f143378750bb29b79ed961ab195cceea50000000000000000000000000000000000000000000000ad78ebc5ac620000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000e36a30d249f7761327fd973001a32010b521b6fd0000000000000000000000005a7facb970d094b6c7ff1df0ea68d99e6e73cbff00000000000000000000000000000000000000000000002086ac351052600000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000084e93ec6170ed630f5ebd89a1aae72d4f63f2713000000000000000000000000e36a30d249f7761327fd973001a32010b521b6fd",
  "2": "2500000"
}
Calldata
#1createRetryableTicket(address,uint256,uint256,address,address,uint256,uint256,bytes)chain 0x1
Target
0x4dbd…ab3f
Value
3269616500000000 wei
Function
createRetryableTicket(address,uint256,uint256,address,address,uint256,uint256,bytes)
Arguments
{
  "0": "0x42480C37B249e33aABaf4c22B20235656bd38068",
  "1": "0",
  "2": "2200010000000000",
  "3": "0x3fB4d38ea7EC20D91917c09591490Eeda38Cf88A",
  "4": "0x3fB4d38ea7EC20D91917c09591490Eeda38Cf88A",
  "5": "2139213",
  "6": "500000000",
  "7": "0x0000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001c000000000000000000000000000000000000000000000000000000000000003e00000000000000000000000000000000000000000000000000000000000000004000000000000000000000000b21b06d71c75973babde35b49ffdac3f82ad3775000000000000000000000000d10b40ff1d92e2267d099da3509253d9da4d715e000000000000000000000000b21b06d71c75973babde35b49ffdac3f82ad3775000000000000000000000000d10b40ff1d92e2267d099da3509253d9da4d715e000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e74313238290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e74313238290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000001e000000000000000000000000000000000000000000000000000000000000000600000000000000000000000009c4ec768c28520b50860ea7a15bd7213a9ff58bf0000000000000000000000002416092f143378750bb29b79ed961ab195cceea500000000000000000000000000000000000000000000004be4e7267b6ae000000000000000000000000000000000000000000000000000000000000000000040000000000000000000000000b21b06d71c75973babde35b49ffdac3f82ad37750000000000000000000000009c4ec768c28520b50860ea7a15bd7213a9ff58bf00000000000000000000000000000000000000000000000000000000000000600000000000000000000000006f7d514bbd4aff3bcd1140b7344b32f063dee4860000000000000000000000002416092f143378750bb29b79ed961ab195cceea500000000000000000000000000000000000000000000022b1c8c1227a00000000000000000000000000000000000000000000000000000000000000000000040000000000000000000000000b21b06d71c75973babde35b49ffdac3f82ad37750000000000000000000000006f7d514bbd4aff3bcd1140b7344b32f063dee486"
}
Calldata
#2sendMessage(address,bytes,uint32)chain 0x1
Target
0x866e…0afa
Value
0 wei
Function
sendMessage(address,bytes,uint32)
Arguments
{
  "0": "0x18281dfC4d00905DA1aaA6731414EABa843c468A",
  "1": "0x000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000260000000000000000000000000000000000000000000000000000000000000000200000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e74313238290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000c0000000000000000000000000000000000000000000000000000000000000006000000000000000000000000046e6b214b524310239732d51387075e0e70970bf0000000000000000000000002416092f143378750bb29b79ed961ab195cceea50000000000000000000000000000000000000000000000ad78ebc5ac62000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000046e6b214b524310239732d51387075e0e70970bf",
  "2": "3000000"
}
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 · 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 ↗