Update tETH price feed on WETH Mainnet market
01Summary
Update the price feed for tETH on the WETH Mainnet market from a tETH/wstETH->ETH/wstETH configuration to tETH/wstETH->wstETH/ETH by calling updateAssetPriceFeed and deploying an upgrade to the Comet protocol.
- Type
- protocol addition
Key changes
- Update tETH price feed on WETH Mainnet market from tETH/wstETH->ETH/wstETH to tETH/wstETH->wstETH/ETH(high)
- Deploy and upgrade Comet proxy at 0xA17581A9E3356d9A858b789D68B4d866e593aE94(high)
Generated by Kvorum
02Description
Update tETH price feed on WETH Mainnet market
Proposal summary
Update price feed for tETH on WETH Mainnet from tETH / wstETH -> ETH / wstETH to tETH / wstETH -> wstETH / ETH.
03Mismatch analysis
The description states a single strategic change: updating the tETH price feed route on the WETH Mainnet Comet market. The calldata contains exactly the two actions expected for this type of change in Compound's governance pattern: (1) updateAssetPriceFeed, which directly implements the described price-feed swap for the tETH asset on a Comet proxy, and (2) deployAndUpgradeTo, which is the standard, mandatory follow-up call used to deploy a new Comet implementation reflecting the updated Configurator state and upgrade the live proxy — this is routine boilerplate for any Configurator-based parameter change and is not separately mentioned in most such proposals, consistent with the 'legitimate summarization' guidance. Both actions target the same cometProxy address, and the Configurator address matches across both calls, so there's no target mismatch. I cannot independently confirm that the specific addresses (asset, cometProxy, newPriceFeed) correspond precisely to 'tETH' and 'WETH Mainnet market' as named in the prose, since the description doesn't include addresses to cross-check, which is why confidence is medium rather than high. However, nothing in the calldata contradicts the description, no extra unrelated actions are present, and no values are omitted that would materially affect DAO funds or control. Overall the actions align well with the stated intent and no discrepancy of note was found.
Generated by Kvorum
04Actions
- Target
- 0x316f…36e3
- Value
- 0 wei
- Function
- updateAssetPriceFeed(address,address,address)
- Arguments
{ "asset": "0xD11c452fc99cF405034ee446803b6F6c1F6d5ED8", "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94", "newPriceFeed": "0x5ECf850c770F78DC7B9f9760672484B2cCAeA818" }- Calldata
- Target
- 0x1ec6…8779
- Value
- 0 wei
- Function
- deployAndUpgradeTo(address,address)
- Arguments
{ "cometProxy": "0xA17581A9E3356d9A858b789D68B4d866e593aE94", "configuratorProxy": "0x316f9708bB98af7dA9c68C1C3b5e79039cD336E3" }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- compoundexecutedUpdate tETH price feed on WETH Mainnet market100%
- compoundexecutedUpdate rsETH and weETH price feeds in cWETHv3 on Mainnet75%
- compoundexecutedReturn rsETH Price Feeds on WETH and wstETH Markets (Mainnet)73%
- compoundexecutedUpdate price feed in cWstETHv3 on Ethereum72%
- compoundexecutedUpdate rsETH Price Feeds on WETH and wstETH Markets (Mainnet)69%
- compoundexecutedUpdate wrsETH Price Feed in cWETHv3 on Linea68%
- aaveexecutedPrice feeds operational update Pt2.5 - wstETH66%
- compoundcanceledUpdate Price Feeds on Arbitrum for LSTs60%
- compoundexecutedUpdate Price Feeds on Arbitrum for LSTs60%