Set WBTC Collateral Factor to 60%
01Summary
Proposal to increase WBTC collateral factor from 40% to 60% on Compound, citing significant growth in WBTC supply (from ~$100M to ~$900M) and liquidity (from ~$1.15M to ~$230M on Uniswap) since the previous increase to 40% in July.
- Type
- parameter change
Key changes
- WBTC collateral factor increased from 40% to 60%(high)
Notable concerns
- WBTC collateral factor remains below DAI, USDC, and ETH (all at 75%)
Generated by Kvorum
02Description
Set WBTC Collateral Factor to 60%
This change increases the Collateral Factor of WBTC from 40% to 60%.
On July 14th, proposal 16 was passed to raise WBTC's Collateral Factor from 0% to 40%. According to Defi Pulse, on July 14th there were ~$100M of WBTC in circulation. Today there are ~$900M of WBTC in circulation. In addition to having a much larger supply today, WBTC liquidity has significantly grown since proposal 16 was passed. Uniswap.info shows WBTC on July 14th with a total liquidity of ~$1.15M while today it has ~$230M.
With this starkly increased liquidity and demand, it makes sense to increase the WBTC collateral factor. Even with this proposed increase to 60%, the WBTC collateral factor would still be significantly under that of DAI, USDC, and ETH, which are each 75%.
We agree with the arguments from proposal 16 that this change would help diversify the set of assets available to borrow on Compound. Now that WBTC has proven itself as a useful asset on Compound, passing this proposal would be a significant improvement to the Compound ecosystem.
03Mismatch analysis
The proposal describes a single action: raising WBTC's collateral factor from 40% to 60% on Compound's Comptroller. The decoded calldata contains exactly one action calling _setCollateralFactor on the Comptroller contract with the cWBTC market address and a value of 600000000000000000, which equals 60% in 18-decimal fixed-point notation (6e17 = 0.6). This numeric value matches the prose claim of 60% after unit conversion. There is no additional action, no unexpected target, and no omitted or extra behavior. The target address pattern (Comptroller calling _setCollateralFactor with a cToken address) is consistent with the standard Compound governance action type described. No value, target, or scope discrepancies were found between the description and the calldata behavior.
Generated by Kvorum
04Actions
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCollateralFactor(address,uint256)
- Arguments
{ "0": "0xC11b1268C1A384e55C48c2391d8d480264A3A7F4", "1": "600000000000000000" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedSet WBTC Collateral Factor to 75%93%
- compounddefeatedSet WBTC Collateral Factor to 65%92%
- compoundcanceledSet WBTC Collateral Factor to 65%92%
- compoundexecutedSet WBTC Collateral Factor to 40%89%
- compoundexecutedZRX, BAT, and WBTC Parameter Update76%
- compounddefeatedAdjust BAT, ZRX collateral factors69%
- compoundexecutedLegacy market maintenance: WBTC and REP65%
- compoundexecutedLegacy market migration: WBTC64%