Add cbBTC as collateral into cUSDCv3 on Base
01Summary
Governance proposal to add cbBTC as collateral to the cUSDCv3 market on Base network. The proposal sends encoded calls to add the asset and upgrade the Comet contract on Base, with risk parameters recommended by Gauntlet based on market simulations.
- Type
- protocol addition
Key changes
- Add cbBTC as collateral asset to cUSDCv3 market on Base network(high)
- Update risk parameters for cbBTC collateral based on Gauntlet recommendations(high)
- Deploy and upgrade Comet contract on Base to support new collateral(high)
Generated by Kvorum
02Description
Add cbBTC as collateral into cUSDCv3 on Base
Proposal summary
Compound Growth Program [AlphaGrowth] proposes to add cbBTC into cUSDCv3 on Base network. This proposal takes the governance steps recommended and necessary to update a Compound III USDC market on Base. 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 off of the recommendations from Gauntlet.
Further detailed information can be found on the corresponding proposal pull request and forum discussion.
Proposal Actions
The first proposal action adds cbBTC to the USDC Comet on Base. This sends the encoded addAsset and deployAndUpgradeTo calls across the bridge to the governance receiver on Base.
03Mismatch analysis
The proposal description states that a single action will add cbBTC as collateral to the Base USDC Comet by sending encoded addAsset and deployAndUpgradeTo calls through the cross-chain bridge to the governance receiver on Base. The single decoded on-chain action is exactly a sendMessage(...) call to the L1CrossDomainMessenger-style bridge, targeting the Base governance receiver address, and the embedded calldata bytes contain the function selectors/signatures for 'addAsset(address,(...))' and 'deployAndUpgradeTo(address,address)', matching the description's mechanical explanation precisely. The description does not assert specific numeric risk parameters (collateral factor, supply caps, etc.) in the prose itself—it only references Gauntlet's forum recommendation by link—so there is no in-description numeric claim to compare against the encoded uint8/uint64/uint128 parameters in the payload, and thus no value_mismatch can be identified from the given text. The target addresses (bridge messenger and Base governance receiver) align with the standard Compound cross-chain governance pattern used for Base market changes, and no extra, omitted, or misdirected actions are apparent. Given the single action's role fully matches the narrative and mechanism described, and no numeric or target discrepancies can be substantiated from the prose alone, this proposal is assessed as consistent with high confidence in the interpretation of the general action, tempered only by inability to verify exact Gauntlet parameter values which the description itself does not enumerate.
Generated by Kvorum
04Actions
- Target
- 0x866e…0afa
- Value
- 0 wei
- Function
- sendMessage(address,bytes,uint32)
- Arguments
{ "0": "0x18281dfC4d00905DA1aaA6731414EABa843c468A", "1": "0x000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000280000000000000000000000000000000000000000000000000000000000000000200000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000046616464417373657428616464726573732c28616464726573732c616464726573732c75696e74382c75696e7436342c75696e7436342c75696e7436342c75696e743132382929000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000000100000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f000000000000000000000000cbb7c0000ab88b473b1f5afd9ef808440eed33bf0000000000000000000000008d38a3d6b3c3b7d96d6536da7eef94a9d7dbc99100000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000b1a2bc2ec5000000000000000000000000000000000000000000000000000000bcbce7f1b1500000000000000000000000000000000000000000000000000000d2f13f7789f0000000000000000000000000000000000000000000000000000000000010c388d00000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f", "2": "3000000" }- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 220x2210…d02e | For | 84.5K | 0.00% | — | 2y ago |
| B90xb933…8dd1 | For | 80K | 0.00% | — | 2y ago |
| 130x13bd…8548 | For | 80K | 0.00% | — | 2y ago |
| 070x0703…961b | For | 80K | 0.00% | — | 2y ago |
| 660x66cd…65f9 | For | 80K | 0.00% | — | 2y ago |
| 3F0x3fb1…4c8a | For | 80K | 0.00% | — | 2y ago |
| B40xb49f…7948 | For | 80K | 0.00% | — | 2y ago |
| B30xb356…c826 | For | 54.6K | 0.00% | — | 2y ago |
| 050x0579…ca09 | For | 50K | 0.00% | — | 2y ago |
| DC0xdc1f…e432 | For | 50K | 0.00% | — | 2y ago |
| 720x72c5…7708 | For | 1.2K | 0.00% | — | 2y ago |
| BE0xbe1d…c953 | For | 231 | 0.00% | — | 2y ago |
| E20xe2a6…325d | For | 100 | 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 |
| D20xd2a7…5a0c | For | 1 | 0.00% | — | 2y ago |
| 950x95f6…2c83 | For | 0.1 | 0.00% | — | 2y ago |
| D80xd8de…ae41 | For | 0.1 | 0.00% | — | 2y ago |
| AF0xafec…c23b | For | 0 | 0.00% | — | 2y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedAdd tBTC as collateral into cUSDCv3 on Base94%
- compoundexecutedAdd cbBTC as collateral into cUSDCv3 on Ethereum94%
- compoundexecutedAdd cbBTC as collateral into cUSDTv3 on Ethereum92%
- compoundexecutedAdd cbBTC as collateral into cWETHv3 on Ethereum90%
- compoundexecutedAdd tBTC as collateral into cUSDCv3 on Mainnet88%
- compoundexecutedAdd tBTC as collateral into cUSDTv3 on Mainnet85%
- compoundexecutedAdd USDC and USDT as collaterals into cWBTCv3 on Mainnet84%
- compoundexecutedAdd WBTC as collateral into cWETHv3 on Mainnet84%
- compoundexecutedAdd tBTC as collateral into cWETHv3 on Mainnet84%
- compoundexecutedAdd tBTC as collateral into cUSDCv3 on Arbitrum82%