KVORUM
compoundSource: Compound governor bravo · #144

Initialize cWETHv3 on Ethereum

executedJan 22, 2023, 01:37 PM UTCbyC60xc66e…68a9

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal initializes a new Compound III WETH market (cWETHv3) on Ethereum by configuring market parameters, setting supply caps for collateral assets (64,500 wstETH and 7,100 cbETH), allocating 38.7 COMP per day to WETH suppliers, seeding the market with 500 WETH reserves, and disabling COMP rewards for the legacy cETH v2 market.

Type
protocol addition

Key changes

  • Initialize cWETHv3 market with configured parameters including supply caps and reward allocation(high)
  • Set cETH v2 COMP reward speeds to zero, deprecating the legacy market(high)
  • Configure market parameters: 64,500 wstETH supply cap, 7,100 cbETH supply cap, 38.7 COMP per day for WETH suppliers(high)
  • Seed new Comet instance with 500 WETH reserves (approximately 358.05 ETH wrapped)(medium)
  • Allocate 25,000 COMP to v3 rewards contract for supply incentives(medium)
  • Deploy new CometFactory implementation and upgrade Comet instance(medium)

Notable concerns

  • Transition from cETH v2 to cWETHv3 requires user migration
  • Market readiness depends on simulations performed with Comet scenario suite
Contracts0x3d9819210a31b4961b30ef54be2aed79b9c9cd3b0x316f9708bb98af7da9c68c1c3b5e79039cd336e30x1ec63b5883c3481134fd50d5daebc83ecd2e87790x1b0e765f6224c21223aea2af16c1c46e38885a400xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc20xA17581A9E3356d9A858b789D68B4d866e593aE94
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

230 words

Initialize cWETHv3 on Ethereum

This proposal takes the governance steps recommended and necessary to initialize a Compound III WETH market; upon execution, cWETHv3 will be ready for use. Simulations have confirmed the market’s readiness, using the Comet scenario suite.

Although the proposal sets the entire configuration in the Configurator, the initial deployment already has most of these same parameters already set. This proposal initializes the market with a supply cap of 64,500 wstETH and 7,100 cbETH, and 38.7 COMP per day allocated to WETH suppliers.

Further detailed information can be found on the corresponding proposal pull request and forum discussion.

Proposal Actions

The first proposal action sets the cETH(v2) COMP reward speeds to zero in the Comptroller.

The second action sets the CometFactory for the new Comet instance in the existing Configurator.

The third action configures the Comet instance in the Configurator.

The fourth action deploys an instance of the newly configured factory and upgrades the Comet instance to use that implementation.

The fifth action configures the existing rewards contract for the newly deployed Comet instance.

The sixth and sevenths actions are to wrap ~358.05 ETH from the Timelock, and transfer the full balance of 500 WETH to the new Comet instance, in order to seed reserves.

The eighth action is to transfer 25,000 an additional COMP to the v3 rewards contract, in order to refresh its supply.

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent

I compared each of the 8 decoded actions against the corresponding narrative in the proposal description. Action 0 (zeroing cETHv2 COMP speeds), action 1 (setFactory), action 3 (deployAndUpgradeTo), action 4 (setRewardConfig), action 5 (wrapping ~358.05 ETH, matching the wei value 358052565869157684316), action 6 (transferring exactly 500 WETH = 500000000000000000000 wei), and action 7 (granting exactly 25,000 COMP = 25000000000000000000000 wei) all match the description's claims precisely, including numeric values after unit conversion. Action 2's setConfiguration call was decoded field-by-field: the two asset configs carry supply caps of 7,100e18 (cbETH) and 64,500e18 (wstETH), matching the stated caps, and the baseTrackingSupplySpeed value (447916666666, scaled by trackingIndexScale 1e15) is consistent with the stated ~38.7 COMP/day emission rate. No target mismatches, no omitted or extra actions, and no misleading characterizations were found. Given the full and accurate correspondence between prose and calldata across all eight actions, the proposal is assessed 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

8 total
#0_setCompSpeeds(address[],uint256[],uint256[])chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_setCompSpeeds(address[],uint256[],uint256[])
Arguments
{
  "0": [
    "0x4Ddc2D193948926D02f9B1fE9e1daa0718270ED5"
  ],
  "1": [
    "0"
  ],
  "2": [
    "0"
  ]
}
Calldata
#1setFactory(address,address)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
setFactory(address,address)
Arguments
{
  "0": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "1": "0xa7F7De6cCad4D83d81676717053883337aC2c1b4"
}
Calldata
#2setConfiguration(address,(address,address,address,address,address,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint104,uint104,uint104,(address,address,uint8,uint64,uint64,uint64,uint128)[]))chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
setConfiguration(address,(address,address,address,address,address,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint64,uint104,uint104,uint104,(address,address,uint8,uint64,uint64,uint64,uint128)[]))
Arguments
{
  "0": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "1": [
    "0x6d903f6003cca6255D85CcA4D3B5E5146dC33925",
    "0xbbf3f1421D886E9b2c5D716B5192aC998af2012c",
    "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2",
    "0xD72ac1bCE9177CFe7aEb5d0516a38c88a64cE0AB",
    "0xe2C1F54aFF6b38fD9DF7a69F22cB5fd3ba09F030",
    "900000000000000000",
    "28382400000000000",
    "606656770600000000",
    "0",
    "900000000000000000",
    "51715000020000000",
    "517150033900000000",
    "9945209674000000",
    "500000000000000000",
    "1000000000000000",
    "447916666666",
    "0",
    "1000000000000000000000",
    "100000000000000000",
    "5000000000000000000000",
    [
      [
        "0xBe9895146f7AF43049ca1c1AE358B0541Ea49704",
        "0x23a982b74a3236A5F2297856d4391B2edBBB5549",
        "18",
        "900000000000000000",
        "930000000000000000",
        "950000000000000000",
        "7100000000000000000000"
      ],
      [
        "0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0",
        "0x4F67e4d9BD67eFa28236013288737D39AeF48e79",
        "18",
        "900000000000000000",
        "930000000000000000",
        "950000000000000000",
        "64500000000000000000000"
      ]
    ]
  ]
}
Calldata
#3deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "0": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3",
  "1": "0xA17581A9E3356d9A858b789D68B4d866e593aE94"
}
Calldata
#4setRewardConfig(address,address)chain 0x1
Target
0x1b0e…5a40
Value
0 wei
Function
setRewardConfig(address,address)
Arguments
{
  "0": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "1": "0xc00e94Cb662C3520282E6f5717214004A7f26888"
}
Calldata
#5fallback()chain 0x1
Target
0xc02a…6cc2
Value
358052565869157684316 wei
Function
fallback()
Arguments
{}
Calldata
#6transfer(address,uint256)chain 0x1
Target
0xc02a…6cc2
Value
0 wei
Function
transfer(address,uint256)
Arguments
{
  "0": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "1": "500000000000000000000"
}
Calldata
#7_grantComp(address,uint256)chain 0x1
Target
0x3d98…cd3b
Value
0 wei
Function
_grantComp(address,uint256)
Arguments
{
  "0": "0x1B0e765F6224C21223AeA2af16c1C46E38885a40",
  "1": "25000000000000000000000"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

AIForum synthesis by Kvorumclaude-sonnet-5
sentiment · favorablethread · constructive

Arguments for

  • The USDC Comet market has proven successful and profitable, justifying deployment of a second Compound III market on Ethereum using WETH as the base asset.— jared
  • Compound III's supply cap mechanism removes illiquidity as a blocking concern, so any asset can be supported as long as the cap and risk parameters are set appropriately.— rleshner
  • On-chain data shows liquid staking derivatives (stETH-type collateral) dramatically increase ETH borrowing demand, indicating strong organic use-case for a wETH Comet market with LSD collateral.— dakeshi
  • Gauntlet's quantitative risk analysis found ample DEX/CEX liquidity for wstETH and manageable insolvency risk for cbETH, supporting safe initial supply caps and risk parameters.— pauljlei
  • Lido offered to share data and analytics support to help inform market design, signaling ecosystem backing for the launch.— Justin_Stables

Arguments against

  • cbETH's liquidity is concentrated off-chain on Coinbase's orderbook, making on-chain arbitrage difficult during liquidations and posing risk if reserves are depleted.— ignaciorsg.eth, 0x7751
  • The proposed interest rate curves imply an unusually high implicit reserve factor (up to 70% at 90% utilization), which would under-incentivize wETH suppliers relative to alternatives like Aave, Morpho, or Euler.— MathisGD, rleshner
  • Gauntlet's original supply cap recommendations were denominated in USD terms set months before deployment, causing a meaningful mismatch (lower caps in ETH terms) once ETH price and liquidity had risen by launch time.— AndrewA
  • The governance cycle is too slow relative to market changes, meaning risk parameters are often outdated by the time they are implemented, requiring repeated future adjustments.— ClairvoyantLabs, RapidsCapital
  • It's unclear whether continuing to launch more Compound III markets (beyond USDC/ETH) is the intended strategic direction, given earlier framing of Compound III as a narrower, lower-risk product distinct from Compound II.— PaulFrambot

Unresolved concerns

  • No concrete mechanism (e.g., a Coinbase-provided onchain backstop bid) was ever implemented to address cbETH's liquidation liquidity risk.— 0x7751, ignaciorsg.eth
  • Whether supply caps should be denominated in ETH rather than USD to remain accurate as ETH price and liquidity shift was raised but not formally adopted before the proposal went live.— AndrewA
  • The broader strategic question of how far Compound III's asset/market scope should expand (versus staying focused on USDC/ETH 'web3 cash') was not directly answered by the team.— PaulFrambot
  • Possibility of automating or speeding up the governance/parameter-update cycle to keep pace with market conditions was suggested but not resolved.— RapidsCapital, ClairvoyantLabs
  • The tradeoff between minimizing negative reserve rate regimes and providing sufficient supply-side incentive was acknowledged as an open, unresolved calibration question pending more data on initial reserve seeding.— pauljlei, rleshner

Notable participants

  • jaredProposer who authored the proposal, managed deployment updates, and responded to community questions throughout.
  • pauljleiGauntlet representative who provided risk parameter analysis, interest rate curve recommendations, and responded to feedback.
  • rleshnerCompound Labs figure who weighed in on interest rate design, reserve factor concerns, and Compound III's risk philosophy.
  • ignaciorsg.ethRaised early technical concerns about cbETH price feed and liquidity risk for liquidations.
  • 0x7751Followed up on cbETH liquidity concerns and proposed a backstop liquidity idea.
  • PaulFrambotQuestioned the strategic scope and direction of expanding Compound III markets.
  • MathisGDIdentified and quantified the high implicit reserve factor issue in Gauntlet's proposed interest rate curves.
  • AndrewARaised questions about interest rate mechanics and highlighted the USD-vs-ETH denomination issue for supply caps.
  • dakeshiProvided on-chain data analysis supporting the case for ETH borrowing demand from liquid staking strategies.
  • Justin_StablesRepresented Lido, offering data and analytical support for the market design discussion.
Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗