KVORUM
aaveSource: Aave governance v3 · #455

Activate Capo Risk Agent and expand Rates Agent on more networks

executedMar 9, 2026, 07:27 AM UTCbyF70xf71f…1e02

01Summary

AISummary by Kvorumclaude-haiku-4-5

This proposal activates the new CAPO Risk Agent on Ethereum to dynamically calibrate price safeguards for yield-bearing assets, and expands the Slope2 Interest Rates Agent to Avalanche, Arbitrum, and Base networks for automated interest rate adjustments. It also aligns interest rate constraints on Ethereum Core and Linea with the new networks (tightening from 4% to 2% for stablecoins and 1.5% for WETH). Additionally, BGD Labs will be reimbursed 108 LINK for Chainlink automation costs.

Type
protocol addition
Funding
$108 LINK reimbursement

Key changes

  • Activate CAPO Risk Agent on Ethereum to dynamically calibrate snapshotRatio (max 3% relative change per 3 days) and maxYearlyRatioGrowthPercent (max 10% relative change per 3 days) for 14 yield-bearing assets including wstETH, weETH, rsETH, osETH, ezETH, cbETH, rETH, tETH, ETHx, LBTC, eBTC, sUSDe, syrupUSDT, and sDAI(high)
  • Expand Slope2 Interest Rates Agent to Avalanche, Arbitrum, and Base networks with constraints of max 2% absolute change per 8 hours for stablecoins (USDC, USDT, USDe) and max 1.5% for WETH(high)
  • Align variableRateSlope2 constraints on Ethereum Core and Linea from 4% to 2% for stablecoins and from 4% to 1.5% for WETH (max absolute change per 8 hours)(medium)
  • Register new agents on AgentHub, configure constrained ranges on RangeValidationModule, assign RISK_ADMIN role to agent contracts, and register Chainlink automation(medium)

Notable concerns

  • CAPO feed parameters on Ethereum are shared across both Core and Prime instances, so changes will affect both instances
  • Tightening of interest rate constraints on Ethereum Core and Linea from 4% to 2% for stablecoins represents more restrictive automated adjustments
ContractsAaveCapoAgentAaveRatesAgentAgentHubRangeValidationModuleCollector
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

888 words

Simple Summary

This proposal activates the new CAPO Risk Agent on Ethereum and expands the existing Slope2 Interest Rates Agent (live on Ethereum Core, Linea) to Avalanche, Arbitrum, and Base networks. Additionally, it aligns the Slope2 Interest Rates Agent constraints on Ethereum Core and Linea with the new networks.

Motivation

Following the successful migration of the AGRS (Risk Stewards) infrastructure to Risk Agents, which activated the Slope2 Interest Rates Agent on Ethereum Core, Linea, it feels natural to expand the Rates Agent on more networks and introduce the new CAPO agent type.

Both initiatives have been suggested by the Risk Service providers on the forum—Slope2 RatesAgent expansion and new CapoAgent addition—along with the latest assets, networks, and constraints for the agents.

CAPO Agent (new)

The CAPO system provides critical price safeguards for yield-bearing assets by defining upper bounds on exchange rates. However, when CAPO parameters remain static for extended periods, the derived maximum ratio can become increasingly detached from real-world exchange rate dynamics, creating vulnerability to price manipulations. By activating the CAPO Risk Agent on Ethereum, parameters like snapshotRatio and maxYearlyRatioGrowthPercent can be dynamically calibrated through the Risk Oracle, maintaining tight and responsive protection for yield-bearing collateral assets without requiring manual governance intervention. More details can be found on the forum post here.

Slope2 Rates Agent (expansion on more networks)

Additionally, extending the Interest Rates Agent to Avalanche, Arbitrum, and Base networks allows for automated adjustment of the variableRateSlope2 parameter on high-utilization assets, ensuring interest rates remain responsive to market conditions across these networks. As part of this expansion, the constraints on Ethereum Core and Linea are updated from 4% to 2% for stablecoins and 1.5% for WETH, aligning them with the new networks. More details can be found on the forum post here.

Specification

The proposal activates the AaveCapoAgent and AaveRatesAgent with the following params using the chaos-agents infra:

CAPO Agent

NetworkAssetsParameterConstraint
EthereumwstETH, weETH, rsETH, osETH, ezETH, cbETH, rETH, tETH, ETHx, LBTC, eBTC, sUSDe, syrupUSDT, sDAIsnapshotRatioMax 3% relative change per 3 days
EthereumwstETH, weETH, rsETH, osETH, ezETH, cbETH, rETH, tETH, ETHx, LBTC, eBTC, sUSDe, syrupUSDT, sDAImaxYearlyRatioGrowthPercentMax 10% relative change per 3 days

Rates Agent

NetworkAssetsParameterConstraint
AvalancheUSDC, USDtvariableRateSlope2Max 2% absolute change per 8 hours
AvalancheWETH.evariableRateSlope2Max 1.5% absolute change per 8 hours
ArbitrumUSDC, USDTvariableRateSlope2Max 2% absolute change per 8 hours
ArbitrumWETHvariableRateSlope2Max 1.5% absolute change per 8 hours
BaseUSDCvariableRateSlope2Max 2% absolute change per 8 hours
BaseWETHvariableRateSlope2Max 1.5% absolute change per 8 hours

Rates Agent Constraint Alignment (Ethereum Core & Linea)

To align the variableRateSlope2 constraints on Ethereum Core and Linea with the new networks:

NetworkAssetsParameterNew ConstraintPrevious Constraint
Ethereum CoreUSDC, USDT, USDevariableRateSlope2Max 2% absolute change per 8 hoursMax 4% absolute change per 8 hours
Ethereum CoreWETHvariableRateSlope2Max 1.5% absolute change per 8 hoursMax 4% absolute change per 8 hours
LineaUSDC, USDTvariableRateSlope2Max 2% absolute change per 8 hoursMax 4% absolute change per 8 hours
LineaWETHvariableRateSlope2Max 1.5% absolute change per 8 hoursMax 4% absolute change per 8 hours

The payload does the following actions:

  • Register new agents on the AgentHub contract by calling registerAgent()
  • Configure constrained ranges on the RangeValidationModule to strictly bound the risk param update from the Chaos Risk Oracle. For Ethereum Core and Linea instances we update the constraints to align with the new networks (2% for stablecoins, 1.5% for WETH).
  • Give RISK_ADMIN role to the AgentContract which will be called by the Chaos Agent system to inject updates onto the Aave protocol.
  • Register new Chainlink automation on the AgentHub Automation wrapper contract for the agents.
  • Reimburse BGD Labs with 108 LINK by withdrawing aLINK from the Collector on Ethereum. BGD Labs previously funded Chainlink automation on Base out of pocket, as the Collector did not hold LINK on that network. The reimbursement also covers costs related to governance automation actions.

Please note: On Ethereum, the following price feeds are shared across both Core and Prime instances: wstETH, rsETH, ezETH, tETH, sUSDe so changes on the capo feed params will be applied to both instances. Since the CAPO feeds use the ACL Manager of both instances, we give the RISK_ADMIN role to the agent contract from both Core and Prime instances.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The decoded on-chain actions consist of only two generic `execute()`/fallback calls to two Ethereum-based payload contracts. This is the standard Aave Governance v3 pattern where a proposal delegatecalls into one or more 'Payload' contracts (here matching the naming of 'AaveV3EthereumPart1' and 'AaveV3EthereumPart2' referenced in the proposal's Implementation links) that contain the actual granular logic (agent registration, RISK_ADMIN role grants, RangeValidationModule constraint updates, Chainlink automation registration, and the LINK reimbursement). Because the calldata does not expose the internal function calls or parameters executed by these payload contracts, it is not possible to verify line-by-line whether the specific numeric constraints (2%, 1.5%, 3%, 10%), asset lists, or the 108 LINK reimbursement amount described in the prose are faithfully implemented on-chain. No contradiction was found between the two visible top-level actions and the description — both are Ethereum-targeted calls consistent with the proposal being split into two parts (Core and Prime instance handling, as explicitly noted in the description for shared CAPO price feeds). However, the description also claims changes on Avalanche, Arbitrum, Base, and Linea, which do not appear as distinct actions in this decoded list; in Aave's cross-chain governance architecture such actions are typically bridged separately from equivalent payloads on those networks and would not necessarily appear in this particular action set, so this is not flagged as a discrepancy but does limit verification depth. Given the opacity of the calldata (no decoded internal calls), confidence in this comparison is low, and no genuine discrepancy is asserted absent more granular data.

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

04Actions

2 total
#0fallback()chain 0x1
Target
0xd163…9561
Value
0 wei
Function
fallback()
Arguments
{}
Calldata
#1fallback()chain 0x1
Target
0x1a4f…914e
Value
0 wei
Function
fallback()
Arguments
{}
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.