KVORUM
compoundSource: Compound governor oz · #526

Update price feeds in cUSDCv3 on Base with CAPO and SVR price feeds.

executedJan 31, 2026, 09:31 AM UTCbyBF0xbfe2…788d

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal updates price feeds for WETH, USDC, cbETH, and wstETH on the USDC market on Base. wstETH is updated to use CAPO (Correlated Assets Price Oracle) to track expected yield growth, while WETH and USDC are updated to support Chainlink's SVR (Sequencer-Validator Redundancy) solution. SVR generates revenue that flows to Compound DAO as protocol fees. CAPO has been audited by OpenZeppelin.

Type
protocol addition

Key changes

  • Update wstETH price feed to CAPO implementation to track liquid staking token yield growth while protecting against price manipulation(high)
  • Update WETH and USDC price feeds to Chainlink SVR implementations following community vote on OEV solution(high)
  • Update cbETH price feed to new implementation on Base market(medium)
  • Configure SVR fee recipient to Compound DAO multisig (0xd9496F2A3fd2a97d8A4531D92742F3C8F53183cB) to capture OEV revenue(medium)
Contracts0x18281dfC4d00905DA1aaA6731414EABa843c468A0xb125e6687d4313864e53df431d5425969c15eb2f0x42000000000000000000000000000000000000060xe6eb5b9b85cff2c84df3de6e7855bc9e76f034d50x3e6d1cca8eee6d02f1f578b613374eb53e6823b40xc1cba3fcea344f92d9239c08c0568f6f2f0ee4520x1738fcae8d5a6aef39985df31fe60e5dc5e1a7b30x2ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec220x0866fc8a76bfc485b8e8c7d543a54bd72f015b1c
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

238 words

Update price feeds in cUSDCv3 on Base with CAPO and SVR price feeds.

Proposal summary

This proposal updates existing price feeds for WETH, USDC, cbETH and wstETH assets on the USDC market on Base.

CAPO summary

CAPO is a price oracle adapter designed to support assets that grow gradually relative to a base asset - such as liquid staking tokens that accumulate yield over time. It provides a mechanism to track this expected growth while protecting downstream protocol from sudden or manipulated price spikes. wstETH price feed is updated to their CAPO implementations.

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, forum discussion for CAPO and forum discussion for SVR.

CAPO audit

CAPO has been audited by [OpenZeppelin](https://www.comp.xyz/t/capo-price-feed-audit/6631, as well as the LST / LRT implementation here.

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, cbETH and wstETH price feeds to the CAPO and SVR implementations. This sends the encoded 'updateAssetPriceFeed', 'setBaseTokenPriceFeed' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Base.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Minor discrepancy

The proposal bridges a single sendMessage call to the Base governance receiver containing 5 sub-calls: 3x updateAssetPriceFeed, 1x setBaseTokenPriceFeed, and 1x deployAndUpgradeTo. This exactly matches the description's stated action types and asset count (WETH, USDC, cbETH, wstETH). Target addresses within the sub-calls consistently reference a single Comet market and a configurator/upgrade address, consistent with a routine multi-asset price-feed update and implementation upgrade, which is standard practice for Compound governance and not something the description needs to spell out further. The one notable gap is the claim about setting an SVR fee recipient to a specific multisig address — no decoded call performs a fee-recipient-setting action; this value is most plausibly baked into the already-deployed SVR feed contract rather than a discrete governance function call, so it's a soft/low-severity omission rather than a sign of malicious redirection. Because we cannot independently verify that the specific addresses in the calldata (feed addresses, asset addresses) correspond exactly to WETH/USDC/cbETH/wstETH and their SVR/CAPO implementations, confidence is medium rather than high. Overall the structure and stated action types line up well with calldata, meriting a 'minor_discrepancy' rating rather than anything more severe.

Discrepancies

  • lowextra in description

    The description states that 'the fee recipient for SVR is set to Compound DAO multisig' as part of this proposal, but no decoded action sets a fee recipient — the five bundled calls are limited to updateAssetPriceFeed, setBaseTokenPriceFeed, and deployAndUpgradeTo. This is likely because the fee recipient is hardcoded into the already-deployed SVR feed contracts rather than set via a separate governance call, but as written the prose could be read as claiming an on-chain action that isn't present in this proposal's calldata.

    “The fee recipient for SVR is set to Compound DAO multisig: 0xd9496F2A3fd2a97d8A4531D92742F3C8F53183cB.”

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0sendMessage(address,bytes,uint32)chain 0x1
Target
0x866e…0afa
Value
0 wei
Function
sendMessage(address,bytes,uint32)
Arguments
{
  "_target": "0x18281dfC4d00905DA1aaA6731414EABa843c468A",
  "_message": "0x00000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000140000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000004a0000000000000000000000000000000000000000000000000000000000000000500000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e58100000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000016000000000000000000000000000000000000000000000000000000000000001c00000000000000000000000000000000000000000000000000000000000000220000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002673657442617365546f6b656e50726963654665656428616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000180000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000060000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f0000000000000000000000004200000000000000000000000000000000000006000000000000000000000000e6eb5b9b85cff2c84df3de6e7855bc9e76f034d50000000000000000000000000000000000000000000000000000000000000040000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f0000000000000000000000003e6d1cca8eee6d02f1f578b613374eb53e6823b40000000000000000000000000000000000000000000000000000000000000060000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f000000000000000000000000c1cba3fcea344f92d9239c08c0568f6f2f0ee4520000000000000000000000001738fcae8d5a6aef39985df31fe60e5dc5e1a7b30000000000000000000000000000000000000000000000000000000000000060000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f0000000000000000000000002ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec220000000000000000000000000866fc8a76bfc485b8e8c7d543a54bd72f015b1c000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000b125e6687d4313864e53df431d5425969c15eb2f",
  "_minGasLimit": "3000000"
}
Calldata

05Tally

Summed from votes

Voters43
VP participating965.1K
Outcome (current)For
Current support100%

06Voters

43 total

No votes recorded yet.

07Forum

AIForum synthesis by Kvorumclaude-sonnet-5
sentiment · mixedthread · constructive

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
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗