KVORUM
compoundSource: Compound governor oz · #508

Update wstETH price feed in cAEROv3 on Base with CAPO implementation.

executedDec 1, 2025, 08:28 AM UTCby870x871f…e26c

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal updates the wstETH price feed in the AERO market on Base to use the CAPO (Correlated Assets Price Oracle) implementation, which is designed to track assets that grow gradually over time like liquid staking tokens while protecting against price manipulation.

Type
protocol addition

Key changes

  • wstETH price feed updated from standard implementation to CAPO implementation on Base AERO market(high)
  • Price oracle adapter deployed to handle gradual asset growth and yield accumulation for liquid staking tokens(high)
  • Protection mechanism added against sudden or manipulated price spikes for wstETH(medium)
Contracts0x45939657d1ca34a8fa39a924b71d28fe8431e5810xbde8f31d2ddda895264e27dd990fab3dc87b372d0x784efeb622244d2348d4f2522f8860b96fbece890xc1cba3fcea344f92d9239c08c0568f6f2f0ee4520x731564585278f228fb8f93a0bf62729e24367662
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

155 words

Update wstETH price feed in cAEROv3 on Base with CAPO implementation.

Proposal summary

This proposal updates existing price feeds for wstETH on the AERO 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.

Further detailed information can be found on the corresponding proposal pull request and forum discussion for CAPO.

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.

Proposal actions

The first action updates wstETH price feed to the CAPO implementation. This sends the encoded 'updateAssetPriceFeed' and 'deployAndUpgradeTo' calls across the bridge to the governance receiver on Base.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal contains a single on-chain action: a cross-chain sendMessage call to the Base governance receiver. Inspecting the encoded bytes, the embedded ABI signatures are literally the strings 'updateAssetPriceFeed(address,address,address)' and 'deployAndUpgradeTo(address,address)', which directly corresponds to the description's claim that the proposal 'sends the encoded updateAssetPriceFeed and deployAndUpgradeTo calls across the bridge to the governance receiver on Base.' This is an exact structural match between the prose and the calldata action names and target (the L2 governance receiver address is consistent with standard Compound cross-chain bridge proposals). I could not fully decode the inner addresses (e.g., confirm the specific wstETH asset address or the exact CAPO price feed address being deployed) without external market-configuration context, so confidence is medium rather than high. However, nothing in the calldata contradicts the description, there are no extra unexplained actions, and no values or targets appear altered from what is claimed. This is a single-action, boilerplate-style cross-chain proposal typical of Compound governance, and the description accurately and narrowly describes what the calldata does.this proposal is consistent.

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": "0x000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000260000000000000000000000000000000000000000000000000000000000000000200000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000bde8f31d2ddda895264e27dd990fab3dc87b372d0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000002d757064617465417373657450726963654665656428616464726573732c616464726573732c61646472657373290000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000236465706c6f79416e6455706772616465546f28616464726573732c616464726573732900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000060000000000000000000000000784efeb622244d2348d4f2522f8860b96fbece89000000000000000000000000c1cba3fcea344f92d9239c08c0568f6f2f0ee452000000000000000000000000731564585278f228fb8f93a0bf62729e24367662000000000000000000000000000000000000000000000000000000000000004000000000000000000000000045939657d1ca34a8fa39a924b71d28fe8431e581000000000000000000000000784efeb622244d2348d4f2522f8860b96fbece89",
  "_minGasLimit": "3000000"
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.