Deprecate pumpBTC from cWBTCv3 on Ethereum
01Summary
Deprecate pumpBTC from cWBTCv3 on Ethereum by updating its price feed to return a minimal price (0.00000001) following the deprecation of its Chainlink oracle, and upgrade Comet to a new version.
- Type
- protocol deprecation
Key changes
- Update pumpBTC price feed from deprecated Chainlink oracle to new price feed returning minimum acceptable price (1e-8)(high)
- Deploy and upgrade Comet to new version on Ethereum(high)
Notable concerns
- Market readiness confirmed through Comet scenario suite simulations, but deprecation of underlying oracle presents operational risk
Generated by Kvorum
02Description
Deprecate pumpBTC from cWBTCv3 on Ethereum
Proposal summary
Woof proposes to deprecate pumpBTC from cWBTCv3 on Ethereum network, since deprecation of its Chainlink oracle.
In order to achieve this price feed will be updated to a new one, which will return the smallest acceptable price - 0.00000001 (1e-8).
This proposal takes the governance steps recommended and necessary to update a Compound III WBTC market on Ethereum. Simulations have confirmed the market’s readiness, as much as possible, using the Comet scenario suite.
Further detailed information can be found on the corresponding proposal pull request.
Proposal Actions
The first proposal action updates pumpBTC price feed to the price feed that returns the smallest acceptable price.
The second action deploys and upgrades Comet to a new version.
03Mismatch analysis
The description states two actions: (1) replace pumpBTC's price feed with one that returns the minimum acceptable price to effectively deprecate the asset, and (2) deploy and upgrade the Comet implementation to finalize the change. The decoded calldata contains exactly two actions in the same order: an updateAssetPriceFeed call targeting the same Configurator and Comet proxy addresses referenced by the description's context (cWBTCv3 on Ethereum), followed by a deployAndUpgradeTo call on the same Comet proxy via the Configurator. Function names, target contracts, and the sequence match the narrative precisely. The specific numeric value of the new price feed's output (1e-8) cannot be independently verified from the calldata since it only references a price feed address rather than a literal price, but this is a standard limitation of oracle-feed proposals and not treated as a discrepancy — the action itself (feed replacement) is faithfully represented. No unexplained extra actions, no omitted actions, and no target or value mismatches were found.
Generated by Kvorum
04Actions
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- updateAssetPriceFeed(address,address,address)
- Arguments
{ "asset": "0xF469fBD2abcd6B9de8E169d128226C0Fc90a012e", "cometProxy": "0xe85Dc543813B8c2CFEaAc371517b925a166a9293", "newPriceFeed": "0x7BaDaB7109afBbF48eCd8d6498CaAcd2630b45B9" }- Calldata
- Target
- 0x1ec6…8779
- Value
- 0 wei
- Function
- deployAndUpgradeTo(address,address)
- Arguments
{ "cometProxy": "0xe85Dc543813B8c2CFEaAc371517b925a166a9293", "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedDeprecate wUSDM from cUSDTv3 on Ethereum82%
- compoundexecutedDeprecate wUSDM from Arbitrum and Optimism markets76%
- compoundexecutedDeprecate stMATIC in cUSDCv3 on Polygon73%
- compoundexecutedDeprecate stMATIC in cUSDTv3 on Polygon72%
- compoundexecutedAdd stMATIC as Collateral to USDCv3 Polygon Market48%
- compounddefeatedAdd stMATIC as Collateral to USDCv3 Polygon Market48%
- compoundexecutedAdd MaticX as Collateral to USDCv3 Polygon Market46%