compoundSource: Compound governor oz · #439
[Gauntlet] Supply Cap Recommendations (04/28/25) pushed by WOOF!
executedMay 10, 2025, 06:03 AM UTCbyBF0xbfe2…788d
01Summary
AISummary by Kvorumclaude-haiku-4-5
Gauntlet recommends increasing supply caps for four assets across Compound V3 markets: weETH on Mainnet USDT Comet (12k to 18k), tETH on Mainnet WETH Comet (4k to 10k), WETH on Unichain USDC Comet (50 to 5k), and UNI on Unichain USDC Comet (7k to 100k). This proposal is submitted by WOOF! on behalf of Gauntlet due to Gauntlet reaching maximum active proposals.
- Type
- parameter change
Key changes
- Increase Mainnet V3 USDT Comet weETH Supply Cap from 12,000 to 18,000(medium)
- Increase Mainnet V3 WETH Comet tETH Supply Cap from 4,000 to 10,000(medium)
- Increase Unichain V3 USDC Comet WETH Supply Cap from 50 to 5,000(high)
- Increase Unichain V3 USDC Comet UNI Supply Cap from 7,000 to 100,000(high)
Notable concerns
- Proposal submitted by WOOF! rather than Gauntlet due to Gauntlet reaching maximum number of active proposals using delegated wallets
Contracts0x316f9708bb98af7da9c68c1c3b5e79039cd336e30x1ec63b5883c3481134fd50d5daebc83ecd2e87790x3Afdc9BCA9213A35503b077a6072F3D0d5AB08400xA17581A9E3356d9A858b789D68B4d866e593aE940x9a3d64e386c18cb1d6d5179a9596a4b5736e98a6
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
02Description
133 words
[Gauntlet] Supply Cap Recommendations (04/28/25) pushed by WOOF!
Simple Summary
Note
This proposal is proposed by WOOF! due to Gauntlet reaching the maximum number of active proposals using their delegated wallets. Live proposals by Gauntlet:
Simple Summary
Gauntlet recommends the following risk recommendations to the protocol:
-
Increase Mainnet V3 USDT Comet’s weETH Supply Cap from 12,000 to 18,000
-
Increase Mainnet V3 WETH Comet’s tETH Supply cap from 4,000 to 10,000
-
Increase Unichain V3 USDC Comet’s WETH Supply cap from 50 to 5,000
-
Increase Unichain V3 USDC Comet’s UNI Supply cap from 7,000 to 100k
Motivation
See full analysis below:
[Gauntlet] - Supply Cap Recommendations
Specification
The proposal updates the parameters by using the respective methods on the Configurator.
03Mismatch analysis
AIMismatch analysis by Kvorumclaude-sonnet-5
Consistent
Compared each decoded action to the four supply-cap increases claimed in the description. Action 0 (Mainnet USDT Comet, weETH asset) sets the cap to 18000e18, matching the claimed increase to 18,000. Action 2 (Mainnet WETH Comet, tETH asset) sets the cap to 10000e18, matching the claimed increase to 10,000. Action 4 is a cross-chain sendMessage to Unichain whose embedded calldata contains two updateAssetSupplyCap calls (decoded via the encoded function selectors and arguments) for WETH (target 0x4200...0006, the standard L2 WETH predeploy) at 5000e18 and UNI at 100000e18, matching the two Unichain claims, plus a deployAndUpgradeTo to finalize both. Actions 1 and 3 are standard deployAndUpgradeTo calls that apply the configurator changes to the comet proxies - this is routine bookkeeping for Compound governance and expected/omitted from the prose without being misleading. No value, target, or direction mismatches were found; all four described supply cap changes are faithfully represented in the calldata, and no undisclosed significant actions (e.g., fund transfers, role grants) are present.
Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
04Actions
5 total
#0updateAssetSupplyCap(address,address,uint128)chain 0x1
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- updateAssetSupplyCap(address,address,uint128)
- Arguments
{ "asset": "0xCd5fE23C85820F7B72D0926FC9b05b43E359b7ee", "cometProxy": "0x3Afdc9BCA9213A35503b077a6072F3D0d5AB0840", "newSupplyCap": "18000000000000000000000" }- Calldata
#1deployAndUpgradeTo(address,address)chain 0x1
- Target
- 0x1ec6…8779
- Value
- 0 wei
- Function
- deployAndUpgradeTo(address,address)
- Arguments
{ "cometProxy": "0x3Afdc9BCA9213A35503b077a6072F3D0d5AB0840", "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3" }- Calldata
#2updateAssetSupplyCap(address,address,uint128)chain 0x1
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- updateAssetSupplyCap(address,address,uint128)
- Arguments
{ "asset": "0xD11c452fc99cF405034ee446803b6F6c1F6d5ED8", "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94", "newSupplyCap": "10000000000000000000000" }- Calldata
#3deployAndUpgradeTo(address,address)chain 0x1
- Target
- 0x1ec6…8779
- Value
- 0 wei
- Function
- deployAndUpgradeTo(address,address)
- Arguments
{ "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94", "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3" }- Calldata
#4sendMessage(address,bytes,uint32)chain 0x1
- Target
- 0x9a3d…98a6
- Value
- 0 wei
- Function
- sendMessage(address,bytes,uint32)
- Arguments
{ "_target": "0x4b5DeE60531a72C1264319Ec6A22678a4D0C8118", "_message": "0x000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000180000000000000000000000000000000000000000000000000000000000000032000000000000000000000000000000000000000000000000000000000000000030000000000000000000000008df378453ff9deffa513367cdf9b3b53726303e90000000000000000000000008df378453ff9deffa513367cdf9b3b53726303e9000000000000000000000000aeb318360f27748acb200ce616e389a6c9409a0700000000000000000000000000000000000000000000000000000000000000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e743132382900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e74313238290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000000600000000000000000000000002c7118c4c88b9841fcf839074c26ae8f035f2921000000000000000000000000420000000000000000000000000000000000000600000000000000000000000000000000000000000000010f0cf064dd5920000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000002c7118c4c88b9841fcf839074c26ae8f035f29210000000000000000000000008f187aa05619a017077f5308904739877ce9ea2100000000000000000000000000000000000000000000152d02c7e14af680000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000008df378453ff9deffa513367cdf9b3b53726303e90000000000000000000000002c7118c4c88b9841fcf839074c26ae8f035f2921", "_minGasLimit": "3000000" }- Calldata
05Tally
Summed from votes
Against0.0%0
For100.0%520.1K
Abstain0.0%0
Voters23
VP participating520.1K
Outcome (current)For
Current support100%
06Voters
23 total
Filter:
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 070x0703…961b | For | 80K | 15.38% | — | 2y ago |
| 3F0x3fb1…4c8a | For | 80K | 15.38% | — | 2y ago |
| B40xb49f…7948 | For | 80K | 15.38% | — | 2y ago |
| 660x66cd…65f9 | For | 80K | 15.38% | — | 2y ago |
| 220x2210…d02e | For | 50K | 9.62% | — | 2y ago |
| 050x0579…ca09 | For | 50K | 9.61% | — | 2y ago |
| B30xb356…c826 | For | 50K | 9.61% | — | 2y ago |
| DC0xdc1f…e432 | For | 50K | 9.61% | — | 2y ago |
| 050x0579…4048 | For | 11.2 | 0.00% | — | 2y ago |
| B90xb933…8dd1 | For | 9.3 | 0.00% | — | 2y ago |
| 370x37b3…f808 | For | 7 | 0.00% | — | 2y ago |
| 4A0x4a46…c1a6 | For | 3 | 0.00% | — | 2y ago |
| 210x21b3…fa75 | For | 2 | 0.00% | — | 2y ago |
| B70xb792…89d7 | For | 2 | 0.00% | — | 2y ago |
| 8B0x8bb9…ccc2 | For | 1.1 | 0.00% | — | 2y ago |
| 010x0151…c3b9 | For | 1.1 | 0.00% | — | 2y ago |
| 170x1729…b879 | For | 1 | 0.00% | — | 2y ago |
| 2F0x2f2f…f78a | For | 0.5 | 0.00% | — | 2y ago |
| C60xc6d7…bfb2 | For | 0.1 | 0.00% | — | 2y ago |
| 610x61ff…9630 | For | 0.1 | 0.00% | — | 2y ago |
| 9A0x9a0f…8de8 | For | 0.1 | 0.00% | — | 2y ago |
| D80xd8de…ae41 | For | 0.1 | 0.00% | — | 2y ago |
| EE0xee3b…4d02 | For | 0 | 0.00% | — | 2y ago |
Showing 23
07Forum
- [Gauntlet] Supply Cap Recommendation Proposals ↗discourse · high confidence
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: 3mo ago
08Similar proposals
AI · embeddings
- compoundexecuted[Gauntlet] - Supply Cap Recommendations (4/14/25)93%
- compoundexecuted[Gauntlet] - Cap recommendations (03/24/25)93%
- compounddefeated[Gauntlet] - Supply Cap Recommendations92%
- compoundexecuted[Gauntlet] Supply Cap Recommendations (11/27/24)92%
- compoundexecuted[Gauntlet' - Supply Cap Recommendations (2024-09-10)92%
- compoundcanceled[Gauntlet] - Supply Cap Recommendations92%
- compoundexecuted[Gauntlet] - Supply Cap Recommendations (6/10/25)92%
- compoundexecuted[Gauntlet] Supply Cap Recommendations (11/4/24)91%
- compoundexecuted[Gauntlet] - Supply Cap Recommendations (2024-09-03)91%
- compoundexecuted[Gauntlet] Supply Cap Recommendations (11/11/24)91%