compoundSource: Compound governor bravo · #380
[Gauntlet] Supply Cap Recommendations (12/09/24)
executedDec 15, 2024, 08:19 AM UTCby4D0x4d80…ef4b
01Summary
AISummary by Kvorumclaude-haiku-4-5
Gauntlet proposes increasing supply caps for cbBTC, wstETH, and LINK across Base V3 and Ethereum V3 USDC Comets to improve capital efficiency. Specifically: Base cbBTC cap increases from 90 to 180, Base wstETH from 700 to 1400, Ethereum LINK from 1,000,000 to 2,000,000, and Ethereum cbBTC from 93 to 180.
- Type
- parameter change
Key changes
- Increase Base V3 USDC Comet cbBTC supply cap from 90 to 180(medium)
- Increase Base V3 USDC Comet wstETH supply cap from 700 to 1400(medium)
- Increase Ethereum V3 USDC Comet LINK supply cap from 1,000,000 to 2,000,000(medium)
- Increase Ethereum V3 USDC Comet cbBTC supply cap from 93 to 180(medium)
Contracts0xc3d688B66703497DAA19211EEdff47f25384cdc30x316f9708bb98af7da9c68c1c3b5e79039cd336e30x1ec63b5883c3481134fd50d5daebc83ecd2e87790x866e82a600a1414e583f7f13623f1ac5d58b0afa
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
02Description
163 words
[Gauntlet] Supply Cap Recommendations (12/09/24)
Summary
Gauntlet recommends the following risk recommendations to the protocol:
- Increase Base V3 USDC Comet’s cbBTC Supply Cap from 90 to 180.
- Increase Base V3 USDC Comet’s wstETH Supply Cap from 700 to 1400.
- Increase Ethereum V3 USDC Comet’s LINK Supply Cap from 1,000,000 to 2,000,000
- Increase Ethereum V3 USDC Comet’s cbBTC Supply Cap from 93 to 180
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 the following 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
4 total
#0updateAssetSupplyCap(address,address,uint128)chain 0x1
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- updateAssetSupplyCap(address,address,uint128)
- Arguments
{ "0": "0xc3d688B66703497DAA19211EEdff47f25384cdc3", "1": "0x514910771AF9Ca656af840dff83E8264EcF986CA", "2": "2000000000000000000000000" }- Calldata
#1updateAssetSupplyCap(address,address,uint128)chain 0x1
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- updateAssetSupplyCap(address,address,uint128)
- Arguments
{ "0": "0xc3d688B66703497DAA19211EEdff47f25384cdc3", "1": "0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf", "2": "18000000000" }- Calldata
#2deployAndUpgradeTo(address,address)chain 0x1
- Target
- 0x1ec6…8779
- Value
- 0 wei
- Function
- deployAndUpgradeTo(address,address)
- Arguments
{ "0": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3", "1": "0xc3d688B66703497DAA19211EEdff47f25384cdc3" }- Calldata
#3sendMessage(address,bytes,uint32)chain 0x1
- Target
- 0x866e…0afa
- Value
- 0 wei
- Function
- sendMessage(address,bytes,uint32)
- Arguments
{ "0": "0x18281dfC4d00905DA1aaA6731414EABa843c468A", "1": "0x0000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001800000000000000000000000000000000000000000000000000000000000000320000000000000000000000000000000000000000000000000000000000000000300000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d00000000000000000000000000000000000000000000000000000000000000030000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e743132382900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d7570646174654173736574537570706c7943617028616464726573732c616464726573732c75696e74313238290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000060000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f000000000000000000000000cbb7c0000ab88b473b1f5afd9ef808440eed33bf0000000000000000000000000000000000000000000000000000000430e234000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f000000000000000000000000c1cba3fcea344f92d9239c08c0568f6f2f0ee45200000000000000000000000000000000000000000000004be4e7267b6ae00000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f", "2": "3000000" }- Calldata
05Tally
Summed from votes
Against0.0%0
For100.0%501.4K
Abstain0.0%0
Voters20
VP participating501.4K
Outcome (current)For
Current support100%
06Voters
20 total
Filter:
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| B90xb933…8dd1 | For | 80K | 15.95% | — | 2y ago |
| 660x66cd…65f9 | For | 80K | 15.95% | — | 2y ago |
| 130x13bd…8548 | For | 80K | 15.95% | — | 2y ago |
| 3F0x3fb1…4c8a | For | 80K | 15.95% | — | 2y ago |
| B40xb49f…7948 | For | 80K | 15.95% | — | 2y ago |
| 220x2210…d02e | For | 50K | 9.97% | — | 2y ago |
| 050x0579…ca09 | For | 50K | 9.97% | — | 2y ago |
| 720x72c5…7708 | For | 1.2K | 0.24% | — | 2y ago |
| BE0xbe1d…c953 | For | 231 | 0.05% | — | 2y ago |
| 050x0579…4048 | For | 11.2 | 0.00% | — | 2y ago |
| B70xb792…89d7 | For | 2 | 0.00% | — | 2y ago |
| 3D0x3ddc…05b0 | For | 1.2 | 0.00% | — | 2y ago |
| 460x4602…8ed7 | For | 1 | 0.00% | — | 2y ago |
| 170x1729…b879 | For | 1 | 0.00% | — | 2y ago |
| 2F0x2f2f…f78a | For | 0.5 | 0.00% | — | 2y ago |
| 6D0x6de8…5dfd | For | 0.2 | 0.00% | — | 2y ago |
| 630x631a…a587 | For | 0.2 | 0.00% | — | 2y ago |
| 290x29bc…d91d | For | 0 | 0.00% | — | 2y ago |
| 290x2917…1339 | For | 0 | 0.00% | — | 2y ago |
| D60xd60e…438c | For | 0 | 0.00% | — | 2y ago |
Showing 20
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: 2mo ago
08Similar proposals
AI · embeddings
- compoundexecuted[Gauntlet] - Cap recommendations (03/24/25)98%
- compoundexecuted[Gauntlet] Supply Cap Recommendations (11/11/24)97%
- compoundexecuted[Gauntlet] Supply Cap Recommendations (11/27/24)97%
- compoundexecuted[Gauntlet] - Cap recommendations (01/21/25)96%
- compoundcanceled[Gauntlet] Supply Cap Recommendations (11/11/24)96%
- compoundexecuted[Gauntlet] Supply Cap Recommendations (11/4/24)96%
- compoundexecuted[Gauntlet] Supply Cap Recommendations - Part 1 (10/24)94%
- compoundexecuted[Gauntlet] - Supply Cap Recommendations (4/14/25)94%
- compoundexecuted[Gauntlet' - Supply Cap Recommendations (2024-09-10)93%
- compoundexecuted[Gauntlet] - Supply Cap Recommendations (2024-09-03)93%