Initialize cWETHv3 on Base
01Summary
This proposal initializes a Compound III WETH market on Base by setting risk parameters recommended by Gauntlet, deploying the necessary contracts, seeding initial reserves with 10 ETH, and reallocating 20 COMP/day from v2 cUSDC borrowers to maintain constant COMP distribution.
- Type
- protocol addition
Key changes
- Initialize cWETHv3 market on Base with risk parameters based on Gauntlet recommendations(high)
- Deploy new Comet implementation for Base WETH market(high)
- Set initial COMP supply speed to 20 COMP/day and borrow speed to 0 COMP/day for cWETHv3(medium)
- Seed cWETHv3 with 10 ETH (wrapped as WETH) as initial reserves(high)
- Reduce COMP distribution to v2 cUSDC borrowers by 20 COMP/day to offset new cWETHv3 incentives(medium)
- Update ENS TXT record to list Base cWETHv3 as official market(low)
Notable concerns
- Initial market readiness dependent on Comet scenario suite simulations
- Reallocation of v2 cUSDC incentives may impact borrowers in that market
Generated by Kvorum
02Description
Initialize cWETHv3 on Base
This proposal takes the governance steps recommended and necessary to initialize a Compound III WETH market on Base; upon execution, cWETHv3 will be ready for use. Simulations have confirmed the market’s readiness, as much as possible, using the Comet scenario suite.
Although the proposal sets the entire configuration in the Configurator, the initial deployment already has most of these same parameters already set. The new parameters include setting the risk parameters based off of the recommendations from Gauntlet for Base as well as their latest recommendations for the WETH market. Finally, the parameters include a modest reallocation of some of the v2 USDC borrow-side COMP incentives to users in the new market.
Further detailed information can be found on the corresponding proposal pull request and forum discussion.
Proposal Actions
The first proposal action sends a cross-chain message to Base, triggering a series of actions. These actions are to set the CometFactory for the new Comet, set the Comet configuration, deploy a new Comet implementation, set COMP as the reward token for the deployment, wrap some ETH to WETH, and transfer WETH to the cWETHv3 contract as initial reserves. The initial supply speed will be 20 COMP/day and borrow speed will be 0 COMP/day.
The second action bridges 10 ETH from the mainnet Timelock to the Base Timelock, to be wrapped as WETH and seeded as initial reserves to the cWETHv3 market.
The third action updates the ENS TXT record v3-official-markets on v3-additional-grants.compound-community-licenses.eth, updating the official markets JSON to include the new Base cUSDbCv3 market.
The fourth action reduces the COMP distribution to v2 cUSDC borrowers by 20 COMP/day, so as to keep the total COMP distribution constant.
03Mismatch analysis
I compared each of the four described proposal actions against the four decoded calldata actions. Action 0 (cross-chain message to Base) matches the description's claim of setting the CometFactory, configuration, deploying the implementation, setting COMP rewards, and seeding WETH reserves — the embedded call signatures (setFactory, setConfiguration, deployAndUpgradeTo, setRewardConfig, deposit, transfer) all correspond to the described steps. Action 1 correctly bridges 10 ETH to the Base Timelock address referenced in action 0's payload, matching the description. Action 3 adjusts COMP speeds on the v2 cUSDC market, consistent with the described reallocation, though exact per-block COMP speed deltas could not be independently verified against a stated 20 COMP/day figure without prior speed values — this is treated as standard bookkeeping, not a discrepancy. The one issue found is in the description of action 2: it states the ENS TXT update adds the new 'cUSDbCv3' market, but this proposal's stated purpose and the calldata's Base network entries indicate the new market being registered is actually WETH (cWETHv3), not USDbC. This looks like a labeling/copy-paste mistake in the prose rather than a functional problem, since the calldata itself correctly lists the new WETH market address. Given this is a naming error only, with no impact on funds, control, or actual on-chain effect, the overall assessment is a minor discrepancy rather than material or severe.
Discrepancies
- lowmisleading phrasing
The description labels the third action's ENS update as adding the 'new Base cUSDbCv3 market' to the official markets registry, but the actual new addition (per the proposal's own stated purpose of initializing cWETHv3) is the WETH market at 0x46e6b214b524310239732D51387075E0e70970bf. The USDbC market entry already appears to be an existing/previously-listed market on Base, not the new one being introduced by this proposal. This appears to be a copy-paste naming error rather than a functional issue, since the calldata correctly includes the WETH market address.
“updating the official markets JSON to include the new Base cUSDbCv3 market”
Generated by Kvorum
04Actions
- Target
- 0x866e…0afa
- Value
- 0 wei
- Function
- sendMessage(address,bytes,uint32)
- Arguments
{ "0": "0x18281dfC4d00905DA1aaA6731414EABa843c468A", "1": "0x00000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000160000000000000000000000000000000000000000000000000000000000000024000000000000000000000000000000000000000000000000000000000000005a0000000000000000000000000000000000000000000000000000000000000000600000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d000000000000000000000000123964802e6ababbe1bc9547d72ef1b69b00a6b100000000000000000000000042000000000000000000000000000000000000060000000000000000000000004200000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008ac7230489e800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000c000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000220000000000000000000000000000000000000000000000000000000000000028000000000000000000000000000000000000000000000000000000000000002c00000000000000000000000000000000000000000000000000000000000000300000000000000000000000000000000000000000000000000000000000000001b736574466163746f727928616464726573732c6164647265737329000000000000000000000000000000000000000000000000000000000000000000000000e6736574436f6e66696775726174696f6e28616464726573732c28616464726573732c616464726573732c616464726573732c616464726573732c616464726573732c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e7436342c75696e743130342c75696e743130342c75696e743130342c28616464726573732c616464726573732c75696e74382c75696e7436342c75696e7436342c75696e7436342c75696e74313238295b5d2929000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000020736574526577617264436f6e66696728616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000096465706f7369742829000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000197472616e7366657228616464726573732c75696e743235362900000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000c000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000520000000000000000000000000000000000000000000000000000000000000058000000000000000000000000000000000000000000000000000000000000005e00000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000004000000000000000000000000046e6b214b524310239732d51387075e0e70970bf00000000000000000000000027c348936400791b7350d80fb81bc61ad68df4ae00000000000000000000000000000000000000000000000000000000000003e000000000000000000000000046e6b214b524310239732d51387075e0e70970bf0000000000000000000000000000000000000000000000000000000000000040000000000000000000000000cc3e7c85bb0ee4f09380e041fee95a0caedd4a020000000000000000000000003cb4653f3b45f448d9100b118b75a1503281d2ee00000000000000000000000042000000000000000000000000000000000000060000000000000000000000009f485610e26b9c0140439f88dc0c7742903bd1cf00000000000000000000000088bb8c109640778d3fb1074bb10a66e31f2c9c170000000000000000000000000000000000000000000000000c7d713b49da00000000000000000000000000000000000000000000000000000064d5a475df8000000000000000000000000000000000000000000000000000086b471e6032da0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c7d713b49da00000000000000000000000000000000000000000000000000000083734dd0b08000000000000000000000000000000000000000000000000000072d49374230d3000000000000000000000000000000000000000000000000000023551d91d5e6800000000000000000000000000000000000000000000000000de0b6b3a764000000000000000000000000000000000000000000000000000000038d7ea4c6800000000000000000000000000000000000000000000000000000000035e55f190900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056bc75e2d63100000000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000010f0cf064dd5920000000000000000000000000000000000000000000000000000000000000000002a000000000000000000000000000000000000000000000000000000000000000010000000000000000000000002ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec2200000000000000000000000059e242d352ae13166b4987ae5c990c232f7f7cd600000000000000000000000000000000000000000000000000000000000000120000000000000000000000000000000000000000000000000c7d713b49da00000000000000000000000000000000000000000000000000000ce80612991d00000000000000000000000000000000000000000000000000000d87e555900180000000000000000000000000000000000000000000000001969368974c05b00000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000046e6b214b524310239732d51387075e0e70970bf000000000000000000000000000000000000000000000000000000000000004000000000000000000000000046e6b214b524310239732d51387075e0e70970bf0000000000000000000000009e1028f5f1d5ede59748ffcee5532509976840e00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000046e6b214b524310239732d51387075e0e70970bf0000000000000000000000000000000000000000000000008ac7230489e80000", "2": "3000000" }- Calldata
- Target
- 0x3154…2c35
- Value
- 10000000000000000000 wei
- Function
- depositETHTo(address,uint32,bytes)
- Arguments
{ "0": "0xCC3E7c85Bb0EE4f09380e041fee95a0caeDD4a02", "1": "200000", "2": "0x" }- Calldata
- Target
- 0x4976…ba41
- Value
- 0 wei
- Function
- setText(bytes32,string,string)
- Arguments
{ "0": "0x7dcf87198fd673716e5a32b206d9379c4fcbad8875073f52bfd0656759bf89ed", "1": "v3-official-markets", "2": "{\"1\":[{\"baseSymbol\":\"USDC\",\"cometAddress\":\"0xc3d688B66703497DAA19211EEdff47f25384cdc3\"},{\"baseSymbol\":\"WETH\",\"cometAddress\":\"0xA17581A9E3356d9A858b789D68B4d866e593aE94\"}],\"137\":[{\"baseSymbol\":\"USDC\",\"cometAddress\":\"0xF25212E676D1F7F89Cd72fFEe66158f541246445\"}],\"8453\":[{\"baseSymbol\":\"USDbC\",\"cometAddress\":\"0x9c4ec768c28520B50860ea7a15bd7213a9fF58bf\"},{\"baseSymbol\":\"WETH\",\"cometAddress\":\"0x46e6b214b524310239732D51387075E0e70970bf\"}],\"42161\":[{\"baseSymbol\":\"USDC\",\"cometAddress\":\"0xA5EDBDD9646f8dFF606d7448e414884C7d905dCA\"}]}" }- Calldata
- Target
- 0x3d98…cd3b
- Value
- 0 wei
- Function
- _setCompSpeeds(address[],uint256[],uint256[])
- Arguments
{ "0": [ "0x39AA39c021dfbaE8faC545936693aC917d5E7563" ], "1": [ "9194444444444444" ], "2": [ "12666666666666667" ] }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- Deploy Compound III on Base ↗discourse · high confidence
- Gauntlet Recommendations: Ethereum Compound v3 ETH - Risk Parameter, IR Curve, & Incentive Changes (8/4/23) ↗discourse · high confidence
Arguments for
- Base is built on the OP Stack with security similar to Optimism, one of the largest L2s, making it a suitable and relatively secure deployment target.— kevin
- Coinbase's popularity with retail users provides an opportunity to onboard a new wave of users to the Compound protocol and position Compound as a core DeFi primitive on Base.— kevin
- Base has demonstrated significant testnet activity with 2.3M accounts created and 24.1M transactions completed, indicating genuine ecosystem development and adoption potential.— kevin
- Aggressive risk parameters should be adopted to ensure Compound remains competitive with other lending protocol deployments on Base.— WintermuteGovernance, Michigan_Blockchain
- Deployment uses proven contract patterns already used on Polygon and Arbitrum, with L1 Timelock governance through a BridgeReceiver ensuring security and decentralization.— kevin
Arguments against
None surfaced.
Unresolved concerns
- Base's sequencer is currently centralized, creating a point of failure for the network.— kevin
- The fraud proof system for Base is still under development and not yet complete.— kevin
- Base core smart contracts can be upgraded by a multi-sig, introducing potential governance and upgrade risks.— kevin
- Parameters are based on assumed testnet TVL and liquidity that may not transfer to mainnet; recommendations must be revisited once mainnet launches and actual liquidity flows in.— Gauntlet
- There is currently no native USDC market on Base, only USDbC (bridged USDC), which provides inferior UX compared to native USDC available on Arbitrum and directly from Coinbase.— gazmagik
Notable participants
- kevinCompound Labs representative who authored the proposal, managed deployments, and provided technical updates throughout the thread.
- GauntletRisk analyst who provided initial parameter recommendations with two options (conservative and aggressive) and ongoing parameter guidance for both markets.
- WintermuteGovernanceCommunity member who expressed support for deployment with preference for aggressive parameters to maintain competitiveness.
- Michigan_BlockchainCommunity member who supported Gauntlet's analysis and endorsed aggressive parameter selection.
- PGovTeam member who managed deployment and initialization of the cWETHv3 market on Base.
- gazmagikCommunity member who raised the concern about native USDC lack and highlighted better UX implications.
Generated by Kvorum
08Similar proposals
- compoundexecutedInitialize cUSDbCv3 on Base92%
- compoundexecutedInitialize cUSDCv3 on Base87%
- compoundexecutedInitialize cUSDSv3 on Base85%
- compoundcanceledInitialize cUSDSv3 on Base85%
- compoundexecutedInitialize cAEROv3 on Base network85%
- compoundexecutedInitialize cUSDCv3 on Polygon83%
- compoundexecutedInitialize cUSDSv3 on Ethereum Mainnet81%
- compoundexecutedInitialize cUSDCv3 on Unichain80%
- compoundcanceledUpdate cWETHv3 and cWstETHv3 Comets on Mainnet to the service patch version80%
- compoundexecutedInitialize cUSDCv3 on Arbitrum79%