We have created an on-chain AIP for this proposal.
Voting will start in approximately 24 hours, participate 
https://vote.onaave.com/proposal/?proposalId=438
2 Likes
POOL_ADMIN renounceRole() by Guardian on pending pools
Simple Summary
After some maturity, it is perfectly safe for the Aave Guardian to renounce the POOL_ADMIN role in relatively new pools: Celo, Soneium, Plasma.
Motivation
Whenever Aave expands to a new network, it does so fully decentralised via an on-chain governance proposal (e.g., Aave v3 Plasma).
Major permissions (upgradeability) of the pool are set to the Aave governance from day 0, but the POOL_ADMIN is given to the Aave Guardian during a period for security.
From a technical/security perspective, we donāt see any risk at the moment or need for the Guardian to hold this role anymore on the aforementioned networks: Celo, Soneium, and Plasma.
Specification
This proposal doesnāt require any governance procedure (Snapshot, on-chain), as the renounce is done directly by the Guardian.
Each instance of the Aave Guardian (Safe) will call the renounceRole() function for the POOL_ADMIN role and its address.
We can confirm the Aave Guardian has renounced the roles on Celo, Soneium and Plasma.
1 Like
Risk Agents maintenance proposal
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 tightens and 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 tightened 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
| Network | Assets | Parameter | Constraint |
|---|---|---|---|
| Ethereum | wstETH, weETH, rsETH, osETH, ezETH, cbETH, rETH, tETH, ETHx, LBTC, eBTC, sUSDe, syrupUSDT, sDAI | snapshotRatio | Max 3% relative change per 3 days |
| Ethereum | wstETH, weETH, rsETH, osETH, ezETH, cbETH, rETH, tETH, ETHx, LBTC, eBTC, sUSDe, syrupUSDT, sDAI | maxYearlyRatioGrowthPercent | Max 10% relative change per 3 days |
Rates Agent
| Network | Assets | Parameter | Constraint |
|---|---|---|---|
| Avalanche | USDC, USDt | variableRateSlope2 | Max 2% absolute change per 8 hours |
| Avalanche | WETH.e | variableRateSlope2 | Max 1.5% absolute change per 8 hours |
| Arbitrum | USDC, USDT | variableRateSlope2 | Max 2% absolute change per 8 hours |
| Arbitrum | WETH | variableRateSlope2 | Max 1.5% absolute change per 8 hours |
| Base | USDC | variableRateSlope2 | Max 2% absolute change per 8 hours |
| Base | WETH | variableRateSlope2 | Max 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:
| Network | Assets | Parameter | New Constraint | Previous Constraint |
|---|---|---|---|---|
| Ethereum Core | USDC, USDT, USDe | variableRateSlope2 | Max 2% absolute change per 8 hours | Max 4% absolute change per 8 hours |
| Ethereum Core | WETH | variableRateSlope2 | Max 1.5% absolute change per 8 hours | Max 4% absolute change per 8 hours |
| Linea | USDC, USDT | variableRateSlope2 | Max 2% absolute change per 8 hours | Max 4% absolute change per 8 hours |
| Linea | WETH | variableRateSlope2 | Max 1.5% absolute change per 8 hours | Max 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_ADMINrole 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.
3 Likes
We have created an on-chain AIP for this proposal.
Voting will start in approximately 24 hours, participate
https://vote.onaave.com/proposal/?proposalId=455
1 Like