KVORUM
compoundSource: Compound governor oz · #556

Cap Recommendations on Ethereum WETH and wstETH comets

executedApr 1, 2026, 08:40 AM UTCby4D0x4d80…ef4b

01Summary

AISummary by Kvorumclaude-haiku-4-5

Gauntlet proposes to reduce supply caps for 11 low-utilization assets across Ethereum WETH and wstETH comets by 50%, including reductions for rswETH, cbBTC, tBTC, osETH, pufETH, ETHx, rETH, cbETH, tETH, ezETH, and weETH.

Type
parameter change

Key changes

  • Reduce rswETH supply cap from 1,000 to 500 on Ethereum WETH comet(medium)
  • Reduce cbBTC supply cap from 150 to 75 on Ethereum WETH comet(medium)
  • Reduce tBTC supply cap from 315 to 157 on Ethereum WETH comet(medium)
  • Reduce osETH supply cap from 10,000 to 2,500 on Ethereum WETH comet(medium)
  • Reduce pufETH supply cap from 4,500 to 2,250 on Ethereum WETH comet(medium)
  • Reduce ETHx supply cap from 2,100 to 1,050 on Ethereum WETH comet(medium)
  • Reduce rETH supply cap from 30,000 to 15,000 on Ethereum WETH comet(medium)
  • Reduce cbETH supply cap from 10,000 to 5,000 on Ethereum WETH comet(medium)

Notable concerns

  • All recommended supply cap reductions are 50%, affecting low-utilization assets
  • Changes require configurator proxy upgrades on both comet instances
Contracts0x3D0bb1ccaB520A66e607822fC55BC921738fAFE30xA17581A9E3356d9A858b789D68B4d866e593aE940x316f9708bb98af7da9c68c1c3b5e79039cd336e30x1ec63b5883c3481134fd50d5daebc83ecd2e8779
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

222 words

Cap Recommendations on Ethereum WETH and wstETH comets

Simple Summary

Gauntlet recommends the following supply cap adjustments to the protocol:

Supply Cap Recommendations

CometAssetSupply Cap
Ethereum WETHrswETH1,000 → 500
Ethereum WETHcbBTC150 → 75
Ethereum WETHtBTC315 → 157
Ethereum WETHosETH10,000 → 2,500
Ethereum WETHpufETH4,500 → 2,250
Ethereum WETHETHx2,100 → 1,050
Ethereum WETHrETH30,000 → 15,000
Ethereum WETHcbETH10,000 → 5,000
Ethereum wstETHtETH5,000 → 2,500
Ethereum wstETHezETH15,000 → 7,500
Ethereum wstETHweETH10,000 → 5,000

Motivation

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

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.xyz/tos

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent

I mapped each of the 11 supply-cap changes listed in the proposal table to the corresponding updateAssetSupplyCap calldata actions, grouping by cometProxy address (0x3D0bb1c... for wstETH's 3 assets: tETH, ezETH, weETH; 0xA17581A9... for WETH's 8 assets). After converting raw uint128 values to human units (accounting for 18-decimal tokens and cbBTC's 8 decimals), every new supply cap in the calldata matches the 'new cap' figures in the description's table exactly. The two deployAndUpgradeTo calls (actions 3 and 12) are standard Compound governance finalization steps that apply the configurator changes to each comet's proxy — this is routine bookkeeping consistent with the proposal's Specification section stating changes are made 'using the respective methods on the Configurator,' and is not something proposers typically call out explicitly. No numeric mismatches, no unexpected targets, and no omitted or extra substantive actions were found. Overall the description is an accurate and complete summary of 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

13 total
#0updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xD11c452fc99cF405034ee446803b6F6c1F6d5ED8",
  "cometProxy": "0x3D0bb1ccaB520A66e607822fC55BC921738fAFE3",
  "newSupplyCap": "2500000000000000000000"
}
Calldata
#1updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xbf5495Efe5DB9ce00f80364C8B423567e58d2110",
  "cometProxy": "0x3D0bb1ccaB520A66e607822fC55BC921738fAFE3",
  "newSupplyCap": "7500000000000000000000"
}
Calldata
#2updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xCd5fE23C85820F7B72D0926FC9b05b43E359b7ee",
  "cometProxy": "0x3D0bb1ccaB520A66e607822fC55BC921738fAFE3",
  "newSupplyCap": "5000000000000000000000"
}
Calldata
#3deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "cometProxy": "0x3D0bb1ccaB520A66e607822fC55BC921738fAFE3",
  "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3"
}
Calldata
#4updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xFAe103DC9cf190eD75350761e95403b7b8aFa6c0",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "500000000000000000000"
}
Calldata
#5updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "7500000000"
}
Calldata
#6updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0x18084fbA666a33d37592fA2633fD49a74DD93a88",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "157000000000000000000"
}
Calldata
#7updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xf1C9acDc66974dFB6dEcB12aA385b9cD01190E38",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "2500000000000000000000"
}
Calldata
#8updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xD9A442856C234a39a81a089C06451EBAa4306a72",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "2250000000000000000000"
}
Calldata
#9updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xA35b1B31Ce002FBF2058D22F30f95D405200A15b",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "1050000000000000000000"
}
Calldata
#10updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xae78736Cd615f374D3085123A210448E74Fc6393",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "15000000000000000000000"
}
Calldata
#11updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xBe9895146f7AF43049ca1c1AE358B0541Ea49704",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "5000000000000000000000"
}
Calldata
#12deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3"
}
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

  • Low utilization markets pose unnecessary risk exposure; reducing caps by 50% for assets averaging below 1% utilization over 30 days decreases protocol risk without affecting current positions.— Gauntlet

Arguments against

None surfaced.

Notable participants

  • GauntletProposer presenting supply cap reduction recommendations based on utilization analysis.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗