Update WETH, USDC, and wstETH price feeds in cAEROv3 on Base with SVR price feeds
01Summary
Update price feeds for WETH, USDC, and wstETH on the AERO market on Base to Chainlink's SVR (Secure Value Recovery) implementation. SVR revenue from liquidators will be received by Compound DAO, with fees directed to the DAO multisig at 0xd9496F2A3fd2a97d8A4531D92742F3C8F53183cB.
- Type
- parameter change
Key changes
- Replace existing WETH price feed with SVR implementation(high)
- Replace existing USDC price feed with SVR implementation(high)
- Replace existing wstETH price feed with SVR implementation(high)
- Enable Compound DAO to receive SVR revenue from liquidators through protocol fees(medium)
Notable concerns
- Implementation follows RFP process and community vote that selected Chainlink's SVR solution
- SVR generates revenue that flows to Compound DAO multisig
- Changes affect critical price feed infrastructure for AERO market on Base
Generated by Kvorum
02Description
Update WETH, USDC, and wstETH price feeds in cAEROv3 on Base with SVR price feeds
Proposal summary
This proposal updates existing price feeds for WETH, USDC, and wstETH assets on the AERO market on Base.
SVR summary
RFP process and community vote passed and decided to implement Chainlink's SVR solution for BASE markets, this proposal updates WETH and USDC price feeds to support SVR implementations.
Further detailed information can be found on the corresponding proposal pull request and forum discussion for SVR.
SVR fee recipient
SVR generates revenue from liquidators and Compound DAO will receive that revenue as part of the protocol fee. The fee recipient for SVR is set to Compound DAO multisig: 0xd9496F2A3fd2a97d8A4531D92742F3C8F53183cB.
Proposal actions
The first action updates WETH, USDC, and wstETH price feeds to the SVR implementation. This sends the encoded 'updateAssetPriceFeed' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Base.
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
- Target
- 0x866e…0afa
- Value
- 0 wei
- Function
- sendMessage(address,bytes,uint32)
- Arguments
{ "_target": "0x18281dfC4d00905DA1aaA6731414EABa843c468A", "_message": "0x0000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001c000000000000000000000000000000000000000000000000000000000000003e0000000000000000000000000000000000000000000000000000000000000000400000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000018000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000784efeb622244d2348d4f2522f8860b96fbece890000000000000000000000004200000000000000000000000000000000000006000000000000000000000000e6eb5b9b85cff2c84df3de6e7855bc9e76f034d50000000000000000000000000000000000000000000000000000000000000060000000000000000000000000784efeb622244d2348d4f2522f8860b96fbece89000000000000000000000000833589fcd6edb6e08f4c7c32d4f71b54bda029130000000000000000000000003e6d1cca8eee6d02f1f578b613374eb53e6823b40000000000000000000000000000000000000000000000000000000000000060000000000000000000000000784efeb622244d2348d4f2522f8860b96fbece89000000000000000000000000c1cba3fcea344f92d9239c08c0568f6f2f0ee4520000000000000000000000001738fcae8d5a6aef39985df31fe60e5dc5e1a7b3000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000784efeb622244d2348d4f2522f8860b96fbece89", "_minGasLimit": "3000000" }- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 3F0x3fb1…4c8a | For | 104.8K | 11.58% | — | 9mo ago |
| 360x36cc…ffc6 | For | 87.6K | 9.68% | — | 9mo ago |
| 540x54a3…e189 | For | 85.1K | 9.40% | — | 9mo ago |
| 660x66cd…65f9 | For | 80K | 8.84% | — | 9mo ago |
| 050x0579…ca09 | For | 60.3K | 6.66% | — | 9mo ago |
| B40xb49f…7948 | For | 60K | 6.63% | — | 9mo ago |
| 170x1729…b879 | For | 60K | 6.63% | — | 9mo ago |
| B70xb792…89d7 | For | 60K | 6.63% | — | 9mo ago |
| D20xd2a7…5a0c | For | 60K | 6.63% | — | 9mo ago |
| B90xb933…8dd1 | For | 60K | 6.63% | — | 9mo ago |
| 8D0x8d07…a265 | For | 55K | 6.08% | — | 9mo ago |
| 070x0703…961b | For | 51.7K | 5.72% | — | 9mo ago |
| 4F0x4f89…fd3c | For | 50K | 5.53% | — | 9mo ago |
| 130x13bd…8548 | For | 30K | 3.31% | — | 9mo ago |
| 1F0x1f3d…0591 | For | 440.7 | 0.05% | — | 9mo ago |
| 220x2210…d02e | For | 35.2 | 0.00% | — | 9mo ago |
| C50xc554…7759 | For | 11.2 | 0.00% | — | 9mo ago |
| 2F0x2f2f…f78a | For | 0.5 | 0.00% | — | 9mo ago |
| EC0xec87…a9a9 | For | 0 | 0.00% | — | 9mo ago |
| DE0xde7d…2990 | For | 0 | 0.00% | — | 9mo ago |
| 880x88f6…0ec0 | For | 0 | 0.00% | — | 9mo ago |
| E00xe005…59d8 | For | 0 | 0.00% | — | 9mo ago |
| D20xd2ab…94cd | For | 0 | 0.00% | — | 9mo ago |
| E50xe570…3510 | For | 0 | 0.00% | — | 9mo ago |
| 7A0x7ac9…73e8 | For | 0 | 0.00% | — | 9mo ago |
| 1C0x1c98…f168 | For | 0 | 0.00% | — | 9mo ago |
| A10xa1a0…0de0 | For | 0 | 0.00% | — | 9mo ago |
| D30xd381…622e | For | 0 | 0.00% | — | 9mo ago |
| 920x9270…db32 | For | 0 | 0.00% | — | 9mo ago |
| DA0xda00…3f51 | For | 0 | 0.00% | — | 9mo ago |
| D40xd4cc…2140 | For | 0 | 0.00% | — | 9mo ago |
| EE0xee3b…4d02 | For | 0 | 0.00% | — | 9mo ago |
| 0F0x0ff1…fa19 | For | 0 | 0.00% | — | 9mo ago |
| 130x13a4…2aaa | For | 0 | 0.00% | — | 9mo ago |
07Forum
- OEV RFP Process Update (July 2025) ↗discourse · high confidence
Arguments for
- Chainlink SVR is already live and proven in production (e.g., with Aave) and Compound already relies on Chainlink feeds on mainnet, so adopting it there adds minimal incremental risk.— cylon, allthecolors, pennblockchain
- Ethereum mainnet holds the largest share of liquidation value, making it the most strategically important and comparatively safe place to pilot an OEV solution first.— cylon
- A phased, single-market rollout on mainnet lets the DAO observe real performance (including through a stress event) before expanding further.— cylon
- Delegates demonstrated decisive support for adopting Chainlink SVR on mainnet through the Snapshot vote, reflecting broad community backing.— AranaDigital
Arguments against
- OEV auctions can add latency to liquidations, and historical price-drawdown data shows even a few blocks of delay can push positions into insolvency, especially on volatile assets and L2s.— Gauntlet, victator
- Empirical analysis of past large Compound liquidations shows that slippage, builder tips, and provider fees consume the vast majority of liquidation incentive, meaning actual recapturable OEV revenue is far smaller than advertised (comparable to a minor SFPF adjustment).— victator
- OEV is a patch over a deeper structural flaw in Compound's liquidation mechanism; resources would be better spent on partial liquidations and mechanism redesign rather than locking in an OEV vendor.— victator
- Committing broadly to any OEV vendor now is premature since solutions are not yet fully tested in live, volatile conditions; a cautious, staged approach with real performance data is preferable.— cylon, Avantgarde
- Chainlink's fairness and prioritization for Compound is questionable given it reportedly offered a materially worse revenue share than to Aave, raising doubts about whether L2 rollout and support will be prioritized.— ugurmersin
Unresolved concerns
- Whether OEV-induced liquidation delays could materially increase insolvency risk on mainnet during high-volatility events once Chainlink SVR is live.— Gauntlet, victator
- Whether real-world OEV revenue capture will be far smaller than projected once slippage, builder tips, and provider fees are accounted for.— victator
- Whether Chainlink SVR's actual latency on mainnet and future L2 rollouts will meet Gauntlet's recommended sub-3-block liquidation window.— Gauntlet, mikemassari
- Unresolved questions about Chainlink's comparatively lower revenue share and prioritization for Compound relative to other protocols like Aave.— ugurmersin
- Whether adopting OEV now risks entrenching an inefficient liquidation architecture rather than pursuing higher-leverage fixes like partial liquidations.— victator
Notable participants
- AranaDigitalOrganized and ran the RFP/Snapshot voting process, provided procedural updates and final vote results.
- cylonDelegate who proposed and iteratively refined a risk-minimized, phased rollout strategy across chains, including supporting Chainlink SVR on mainnet.
- GauntletProvided quantitative risk analysis on liquidation latency and price drawdowns, recommending caution and a 3-block latency ceiling.
- victatorAuthored a detailed risk-first analysis (Platonia) arguing OEV revenue is overestimated and that liquidation mechanism redesign is a higher priority than OEV adoption.
- ugurmersinApi3 representative who defended Api3's production track record and raised pointed questions about Chainlink and RedStone's claims and incentives.
- mikemassariRedStone representative who responded to latency/searcher-network critiques and defended RedStone's Venus pilot record.
- allthecolorsDelegate who largely aligned with cylon's cautious approach but advocated testing Chainlink SVR on Base and keeping Api3 on Mantle.
- pennblockchainDelegate who voted with a measured rollout stance, initially favoring Api3 on Arbitrum before revising to no deployment there.
- AvantgardeDelegate who echoed cylon's cautious, phased-testing approach given immature state of OEV solutions.
Generated by Kvorum
08Similar proposals
- compoundexecutedUpdate USDC and cbBTC price feeds in cWETHv3 on Base with SVR price feeds.94%
- compoundexecutedUpdate price feeds in cUSDCv3 on Base with CAPO and SVR price feeds.92%
- compoundexecutedUpdate price feeds in cUSDCv3 on Base with CAPO and SVR price feeds.91%
- compoundexecutedUpdate cbBTC price feeds on Base to SVR88%
- compoundexecutedUpdate price feeds in cUSDCv3 on Arbitrum with SVR price feeds.87%
- compoundexecutedUpdate price feeds in cUSDSv3 on Mainnet with CAPO and Chainlink SVR implementation.86%
- compoundexecutedUpdate price feeds in cWETHv3 on Arbitrum with SVR and CAPO price feeds.85%
- compoundexecutedUpdate price feeds in cUSDCv3 on Mainnet with CAPO and Chainlink SVR implementation.85%
- compoundexecutedUpdate price feeds in cUSDTv3 on Mainnet with CAPO and Chainlink SVR implementation.84%
- compoundexecutedUpdate price feeds in cUSDTv3 on Arbitrum with CAPO and SVR price feeds.84%