Add COMP Support
01Summary
This proposal adds Compound (COMP) token as a supported asset in the protocol by deploying cCOMP contract with a JumpRateModelV2 interest rate model, setting a 60% collateral factor, 20% reserve factor, and a 50k COMP borrowing cap.
- Type
- protocol addition
Key changes
- Add cCOMP as a supported market using existing proven cUNI implementation code(high)
- Deploy JumpRateModelV2 with 2% base borrow rate, 20% rate at 80% kink, and 100% at 100% utilization(high)
- Set collateral factor to 60% for cCOMP(high)
- Set reserve factor to 20% for cCOMP(medium)
- Implement 50k COMP borrowing cap(medium)
Generated by Kvorum
02Description
Add COMP Support
This proposal adds Compound as a supported asset.
The cCOMP contract was deployed using existing, proven code. The implementation contract is the same contract as the cUNI implementation contract.
cCOMP uses a new JumpRateModelV2 interest rate model with the following parameters:
- 2% APY borrow base rate
- 20% APY borrow rate at kink
- Kink at 80% utilization
- 100% APY borrow rate at 100% utilization
The collateral factor for cCOMP is set to 60% and the reserve factor is set to 20%. A borrowing cap of 50k COMP is set as well.
03Mismatch analysis
I compared each decoded action against the prose claims. Action 0 (_supportMarket) matches the stated goal of listing cCOMP. Action 2's collateral factor (600000000000000000 = 60%) matches the stated 60% collateral factor. Action 3's reserve factor (200000000000000000 = 20%) matches the stated 20% reserve factor. Action 4's borrow cap (50000000000000000000000, i.e., 50,000 * 1e18, consistent with COMP's 18 decimals) matches the stated 50k COMP borrow cap. The interest rate model parameters described (base rate, kink, rates at kink/100% utilization) are not represented as separate governance actions because they are set at cCOMP contract deployment time, not via this governance calldata — this is expected and not a discrepancy. The only unmentioned action is _addCompMarkets (action 1), which enables COMP reward distribution for the new market; this is routine, low-risk boilerplate for adding any new Compound market and doesn't materially change the risk profile or contradict the description. Overall, all material financial parameters (collateral factor, reserve factor, borrow cap) and the core action (adding the market) are accurately and correctly represented in the description matching the calldata precisely after unit conversion.'
Discrepancies
- lowomitted in description
The calldata includes an _addCompMarkets call registering cCOMP for COMP reward distribution, which is not explicitly mentioned in the description. However, this is standard boilerplate when adding a new Compound market and does not represent a hidden or harmful action.
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _supportMarket(address)
- Arguments
{ "0": "0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _addCompMarkets(address[])
- Arguments
{ "0": [ "0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4" ] }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4", "1": "600000000000000000" }- Calldata
- Target
- 0x70e3…e8e4
- Value
- 0 wei
- Function
- _setReserveFactor(uint256)
- Arguments
{ "0": "200000000000000000" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setMarketBorrowCaps(address[],uint256[])
- Arguments
{ "0": [ "0x70e36f6BF80a52b3B46b3aF8e106CC0ed743E8e4" ], "1": [ "50000000000000000000000" ] }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- Proposal 27: Adding COMP as an asset ↗discourse · high confidence
Arguments for
- COMP as a collateral asset follows the successful precedent of cUNI with identical risk parameters (60% collateral factor, 20% reserve factor) and proper technical implementation.— arr00
- The cCOMP contract uses the same battle-tested CCompLikeDelegate implementation as cUNI, reducing implementation risk.— arr00
- A new price feed is not required since the existing price feed already supports COMP, simplifying the addition.— arr00
- The addition has been simulated in a fork using a Compound-standard notebook to verify expected behavior.— arr00
Arguments against
None surfaced.
Unresolved concerns
- Whether users can supply delegated COMP to cCOMP while retaining voting power, or if supplying COMP breaks delegation.— suspect78
- The implications of cCOMP holders potentially losing voting rights on market liquidity COMP unless future governance changes enable that capability.— suspect78
Notable participants
- arr00Proposal author who provided technical specifications, deployed contracts, and addressed community questions.
- suspect78Community member who raised clarifying questions about delegation and voting mechanics with supplied COMP.
Generated by Kvorum
08Similar proposals
- compoundexecutedCOMP Distribution Patch74%
- compoundexecutedDistribute COMP to Users73%
- compoundexecutedSplit COMP rewards distribution and bug fixes70%
- compoundexecutedEnd cCOMP Borrow Rewards70%
- compoundexecutedInitialize Compound III COMP Distribution70%
- compoundexecutedFix COMP Accrual Bug68%
- compoundexecutedReduce COMP emissions by 20%67%
- compounddefeatedRefresh Polygon COMP67%
- compoundexecutedAdjusting COMP distribution speed to match Ethereum network block time and increasing higher-risk assets Reserve Factor66%
- compoundexecutedRefresh Polygon COMP66%