[Gauntlet] Compound v2 Deprecation Phase 11 (2024-04-15)
01Summary
Gauntlet proposes Phase 11 of Compound v2 deprecation by reducing collateral factors for 9 assets by 5 percentage points each (AAVE 38%→33%, BAT 45%→40%, COMP 25%→20%, LINK 44%→39%, MKR 38%→33%, SUSHI 32%→27%, UNI 75%→70%, YFI 40%→35%, ZRX 30%→25%) to further wind down the v2 market.
- Type
- parameter change
Key changes
- AAVE collateral factor decreased from 38% to 33%(medium)
- BAT collateral factor decreased from 45% to 40%(medium)
- COMP collateral factor decreased from 25% to 20%(medium)
- LINK collateral factor decreased from 44% to 39%(medium)
- MKR collateral factor decreased from 38% to 33%(medium)
- SUSHI collateral factor decreased from 32% to 27%(medium)
- UNI collateral factor decreased from 75% to 70%(high)
- YFI collateral factor decreased from 40% to 35%(medium)
Notable concerns
- Reduced collateral factors may force liquidations for users with leveraged positions in v2 assets
- These parameter changes continue the deprecation of v2, directing users toward v3
Generated by Kvorum
02Description
[Gauntlet] Compound v2 Deprecation Phase 11 (2024-04-15)
Simple Summary
For Phase 11 of the Compound v2 deprecation, Gauntlet recommends decreasing the Collateral Factor for v2 collateral assets. Specifically, Gauntlet recommends the following changes:
- Decrease AAVE Collateral Factor from 38% to 33%
- Decrease BAT Collateral Factor from 45% to 40%
- Decrease COMP Collateral Factor from 25% to 20%
- Decrease LINK Collateral Factor from 44% to 39%
- Decrease MKR Collateral Factor from 38% to 33%
- Decrease SUSHI Collateral Factor from 32% to 27%
- Decrease UNI Collateral Factor from 75% to 70%
- Decrease YFI Collateral Factor from 40% to 35%
- Decrease ZRX Collateral Factor from 30% to 25%
For more details, see the full forum post here.
Motivation
In this September 2022 snapshot vote, the community voted that each asset’s Collateral Factor may be reduced by an absolute percentage of up to 5%. After our analysis, Gauntlet recommends this max 5% decrease for each stated collateral asset in order to further deprecate the v2 market. Full proposal and forum discussion
Specification
The proposal updates the parameters using the _setCollateralFactor method of the relevant cToken contracts.
<sub>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.<sub>
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0xe65cdB6479BaC1e22340E4E755fAE7E509EcD06c", "1": "330000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x6C8c6b02E7b2BE14d4fA6022Dfd6d75921D90E4E", "1": "400000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4", "1": "200000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0xFAce851a4921ce59e912d19329929CE6da6EB0c7", "1": "390000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x95b4eF2869eBD94BEb4eEE400a99824BF5DC325b", "1": "330000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x4B0181102A0112A2ef11AbEE5563bb4a3176c9d7", "1": "270000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x35A18000230DA775CAc24873d00Ff85BccdeD550", "1": "700000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x80a2AE356fc9ef4305676f7a3E2Ed04e12C33946", "1": "350000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0xB3319f5D18Bc0D84dD1b4825Dcde5d5f7266d407", "1": "250000000000000000" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- [Gauntlet] - Compound v2 Deprecation Phase 11 (04/12/2024) ↗discourse · high confidence
Arguments for
- Collateral Factor reductions support the community-approved v2 deprecation strategy and do not immediately cause new liquidations.— Gauntlet
Arguments against
None surfaced.
Unresolved concerns
- Whether the collateral factor reductions will cause risk-off liquidations or significant health factor degradation for affected users over time.— Gauntlet
Notable participants
- GauntletProposer and risk analyst recommending phased v2 collateral factor reductions.
Generated by Kvorum
08Similar proposals
- compoundexecuted[Gauntlet] Compound v2 Deprecation Phase 11 (2024-04-22)100%
- compoundexecuted[Gauntlet] 2024-02-12: Compound v2 Deprecation (Phase 9)99%
- compoundexecuted[Gauntlet] - Compound v2 Deprecation Phase 12 (05/20/2024)99%
- compoundexecuted[Gauntlet] 2023-11-13: Compound v2 Deprecation (Phase 4)97%
- compoundexecuted[Gauntlet] 2023-10-30: Compound v2 Deprecation (Phase 3)96%
- compoundexecutedCompound v2 Deprecation Phase 1396%
- compoundexecuted[Gauntlet] 2024-01-29: Compound v2 Deprecation (Phase 8)96%
- compoundexecuted[Gauntlet] 2023-12-04: Compound v2 Deprecation (Phase 5)94%
- compoundexecuted[Gauntlet] 2023-01-14: Compound v2 Deprecation (Phase 7)94%
- compoundexecuted[Gauntlet] 2023-10-09: Compound v2 Deprecation (Phase 2)94%