KVORUM
compoundSource: Compound governor oz · #599

Set Zero Supply Caps for Low-Demand LST/LRT Collateral on Ethereum

executedAug 30, 2026, 07:36 AM UTCby4D0x4d80…ef4b

01Summary

AISummary by Kvorumclaude-haiku-4-5

Gauntlet recommends setting supply caps to zero for three low-demand liquid staking token/liquid restaking token collaterals (pufETH, ezETH, and tETH) across Ethereum WETH and wstETH Comets. This prevents new deposits of these assets while allowing existing positions to continue operating normally, with no forced liquidations or changes to collateral factors.

Type
parameter change

Key changes

  • Set pufETH supply cap on Ethereum WETH Comet from 105 to 0(medium)
  • Set ezETH supply cap on Ethereum WETH Comet from 500 to 0(medium)
  • Set tETH supply cap on Ethereum wstETH Comet from 44 to 0(medium)

Notable concerns

  • Existing collateral balances and positions will continue to operate, but new deposits of affected collateral will be blocked
Contracts0xA17581A9E3356d9A858b789D68B4d866e593aE940x3D0bb1ccaB520A66e607822fC55BC921738fAFE3
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

247 words

Set Zero Supply Caps for Low-Demand LST/LRT Collateral on Ethereum

Summary

Gauntlet recommends setting the supply caps to 0 for three low-demand LST/LRT collateral listings across the Ethereum WETH and wstETH Comets.

Proposed Changes

CometCollateralCurrent Supply CapProposed Supply Cap
Ethereum WETHpufETH1050
Ethereum WETHezETH5000
Ethereum wstETHtETH440

Setting a supply cap to 0 prevents users from depositing additional units of the affected collateral into the corresponding Comet.

This proposal does not:

  • Force liquidations.
  • Change collateral or liquidation factors.
  • Prevent withdrawals or repayments.
  • Affect existing collateral balances.

Existing positions will continue to operate normally, and users will retain the ability to repay debt and withdraw collateral.

Proposal Actions

  1. Set the pufETH supply cap on the Ethereum WETH Comet to 0.
  2. Set the ezETH supply cap on the Ethereum WETH Comet to 0.
  3. Deploy and upgrade the Ethereum WETH Comet to apply the updated configuration.
  4. Set the tETH supply cap on the Ethereum wstETH Comet to 0.
  5. Deploy and upgrade the Ethereum wstETH Comet to apply the updated configuration.

Additional Information

For the complete motivation, methodology, risk considerations, and supporting data, see the Compound V3 ETH Comets: Zero Supply Caps for Low-Demand LST/LRT Collateral forum post.

03Mismatch analysis

AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent

The proposal describes five sequential actions: two supply-cap-to-zero updates on the WETH Comet (pufETH, ezETH), an upgrade of the WETH Comet to apply them, one supply-cap-to-zero update on the wstETH Comet (tETH), and an upgrade of the wstETH Comet. The decoded calldata contains exactly five actions in the same order: two updateAssetSupplyCap calls targeting the Configurator with cometProxy = 0xA175... (the known Compound WETH Comet address) and newSupplyCap = 0, followed by a deployAndUpgradeTo call for the same cometProxy; then one updateAssetSupplyCap call with cometProxy = 0x3D0b... (the known wstETH Comet address) and newSupplyCap = 0, followed by a deployAndUpgradeTo call for that proxy. All targets, function signatures, and parameter values (supply cap set to 0) align precisely with the prose. No extra actions, missing actions, or value/target mismatches were found. Confidence is high because the comet proxy addresses match well-known Compound V3 Ethereum WETH and wstETH markets and the action sequence and count match one-to-one with the description's numbered list.

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

04Actions

5 total
#0updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xD9A442856C234a39a81a089C06451EBAa4306a72",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "0"
}
Calldata
#1updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xbf5495Efe5DB9ce00f80364C8B423567e58d2110",
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "newSupplyCap": "0"
}
Calldata
#2deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94",
  "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3"
}
Calldata
#3updateAssetSupplyCap(address,address,uint128)chain 0x1
Target
0x316f…36e3
Value
0 wei
Function
updateAssetSupplyCap(address,address,uint128)
Arguments
{
  "asset": "0xD11c452fc99cF405034ee446803b6F6c1F6d5ED8",
  "cometProxy": "0x3D0bb1ccaB520A66e607822fC55BC921738fAFE3",
  "newSupplyCap": "0"
}
Calldata
#4deployAndUpgradeTo(address,address)chain 0x1
Target
0x1ec6…8779
Value
0 wei
Function
deployAndUpgradeTo(address,address)
Arguments
{
  "cometProxy": "0x3D0bb1ccaB520A66e607822fC55BC921738fAFE3",
  "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total
Filter:
VoterChoice% of totalRationale
660x66cd…65f9for80.2K0.00%—2mo ago
3F0x3fb1…4c8afor80K0.00%—2mo ago
B40xb49f…7948for60K0.00%—2mo ago
050x0579…ca09for60K0.00%—2mo ago
B70xb792…89d7for60K0.00%—2mo ago
B90xb933…8dd1for60K0.00%—2mo ago
170x1729…b879for60K0.00%—2mo ago
D20xd2a7…5a0cfor60K0.00%—2mo ago
B30xb356…c826for59K0.00%—2mo ago
070x0703…961bfor51.7K0.00%—2mo ago
1F0x1f3d…0591for440.70.00%—2mo ago
E90xe93d…e2b5for5.90.00%—2mo ago
9F0x9f77…2768for10.00%—2mo ago
2F0x2f2f…f78afor0.50.00%—2mo ago
Showing 14

07Forum

No forum thread is confidently linked to this proposal.