Add tBTC as collateral into cWETHv3 on Mainnet
01Summary
Add tBTC as collateral to the cWETHv3 market on Ethereum mainnet with risk parameters recommended by Gauntlet. This involves adding tBTC as an asset with specific configuration settings and upgrading the Comet contract to a new version.
- Type
- protocol addition
Key changes
- Add tBTC (0x18084fbA666a33d37592fA2633fD49a74DD93a88) as collateral asset to cWETHv3 market(high)
- Set tBTC collateral factor at 76% with liquidation threshold at 81% and liquidation incentive at 90%(high)
- Deploy and upgrade Comet to new version to enable tBTC collateral support(high)
Notable concerns
- Market readiness validated through Comet scenario suite simulations
- Risk parameters based on Gauntlet recommendations
Generated by Kvorum
02Description
Add tBTC as collateral into cWETHv3 on Mainnet
Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add tBTC into cWETHv3 on Ethereum network. This proposal takes the governance steps recommended and necessary to update a Compound III WETH market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the Comet scenario suite. The new parameters include setting the risk parameters based on the recommendations from Gauntlet.
Further detailed information can be found on the corresponding proposal pull request and forum discussion.
Proposal Actions
The first action adds tBTC asset as collateral with corresponding configurations.
The second action deploys and upgrades Comet to a new version.
03Mismatch analysis
The description states two actions: (1) adding tBTC as collateral with risk parameters, and (2) deploying and upgrading the Comet implementation to activate the new configuration. The decoded calldata contains exactly two actions matching this: an addAsset call on the Configurator contract targeting the same market address (0xA175...94) with a new asset config (price feed, collateral factors, supply cap), followed by a deployAndUpgradeTo call that upgrades the same market proxy address using the Configurator. The market address referenced in action 0 (as the market being configured) matches the address being upgraded in action 1, confirming they operate on the same cWETHv3 market as described. No numeric risk parameters are explicitly stated in the prose (it defers to the linked Gauntlet recommendations and forum post), so there is nothing to directly compare for value mismatches — this is legitimate summarization rather than omission. No extra, missing, or misdirected actions were found. Overall the proposal description accurately and completely reflects the two on-chain actions.
Generated by Kvorum
04Actions
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- addAsset(address,(address,address,uint8,uint64,uint64,uint64,uint128))
- Arguments
{ "0": "0xA17581A9E3356d9A858b789D68B4d866e593aE94", "1": [ "0x18084fbA666a33d37592fA2633fD49a74DD93a88", "0x1933F7e5f8B0423fbAb28cE9c8C39C2cC414027B", "18", "760000000000000000", "810000000000000000", "900000000000000000", "315000000000000000000" ] }- Calldata
- Target
- 0x1ec6…8779
- Value
- 0 wei
- Function
- deployAndUpgradeTo(address,address)
- Arguments
{ "0": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3", "1": "0xA17581A9E3356d9A858b789D68B4d866e593aE94" }- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 220x2210…d02e | For | 81.5K | 11.34% | — | 2y ago |
| B90xb933…8dd1 | For | 80K | 11.14% | — | 2y ago |
| 130x13bd…8548 | For | 80K | 11.14% | — | 2y ago |
| 070x0703…961b | For | 80K | 11.14% | — | 2y ago |
| 660x66cd…65f9 | For | 80K | 11.14% | — | 2y ago |
| 3F0x3fb1…4c8a | For | 80K | 11.14% | — | 2y ago |
| B40xb49f…7948 | For | 80K | 11.14% | — | 2y ago |
| B30xb356…c826 | For | 54.7K | 7.61% | — | 2y ago |
| 050x0579…ca09 | For | 50K | 6.96% | — | 2y ago |
| 4F0x4f89…fd3c | For | 50K | 6.96% | — | 2y ago |
| 720x72c5…7708 | For | 1.2K | 0.17% | — | 2y ago |
| 5C0x5c04…dc62 | For | 671.8 | 0.09% | — | 2y ago |
| BE0xbe1d…c953 | For | 231 | 0.03% | — | 2y ago |
| E20xe2a6…325d | For | 100 | 0.01% | — | 2y ago |
| E40xe459…e666 | For | 5.2 | 0.00% | — | 2y ago |
| 210x21b3…fa75 | For | 2 | 0.00% | — | 2y ago |
| B70xb792…89d7 | For | 2 | 0.00% | — | 2y ago |
| 170x1729…b879 | For | 1 | 0.00% | — | 2y ago |
| E30xe364…5413 | For | 0.1 | 0.00% | — | 2y ago |
| 280x2817…24f1 | For | 0.1 | 0.00% | — | 2y ago |
| 980x98c4…d544 | For | 0 | 0.00% | — | 2y ago |
| 480x48f2…f356 | For | 0 | 0.00% | — | 2y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedAdd tBTC as collateral into cUSDTv3 on Mainnet96%
- compoundexecutedAdd tBTC as collateral into cUSDCv3 on Mainnet95%
- compoundexecutedAdd cbBTC as collateral into cWETHv3 on Ethereum94%
- compoundexecutedAdd WBTC as collateral into cWETHv3 on Mainnet94%
- compoundexecutedAdd cbBTC as collateral into cUSDTv3 on Ethereum93%
- compoundexecutedAdd cbBTC as collateral into cUSDCv3 on Ethereum90%
- compoundexecutedAdd USDC and USDT as collaterals into cWBTCv3 on Mainnet85%
- compoundexecutedAdd tBTC as collateral into cUSDCv3 on Base85%
- compoundexecutedAdd WBTC as collateral into cWETHv3 on Arbitrum85%
- compoundexecutedAdd cbBTC as collateral into cUSDCv3 on Base84%