Caps Risk Oracle Activation on Arbitrum
Caps Risk Oracle Activation on Arbitrum
Author
BGD Labs (@bgdlabs)
Creator
0xf71fc92e2949ccF6A5Fd369a0b402ba80Bc61E02
Simple Summary
This proposal activates the automated Aave Generalized Risk Stewards (AGRS) system on the Arbitrum Instance to perform automated supply and borrow cap updates. Under the hood, the AGRS consumes risk recommendations from the Edge infrastructure by Chaos Labs.
Motivation
The current implementation of manual AGRS allows for the periodic manual updating of Supply and Borrow caps, generally performed in response to market demand. The high volume of updates, combined with the manual triggering of supply and borrow cap simulations, written analyses, and coordination across multiple service providers, often leads to delays in implementing cap increases. These delays can hinder potential growth opportunities for underlying assets that might otherwise contribute significantly, but more importantly, they create overhead to have tighter risk configurations and dynamism.
This new component of AGRS follows the example of interest rate updates for WETH on v3 Prime Ethereum (this proposal, in production for some time.
Specification
The automated AGRS will use another instance of AGRS (exactly the same codebase as the other model), but with the following constraints:
- This instance will only have configurable caps-related parameters: supplyCap and borrowCap.
- Recommendations of these parameters will be submitted to a RiskOracle smart contract, from the Edge off-chain infrastructure.
- Between the risk oracle smart contract and the AGRS contract, there will be a very thin middleware AaveStewardCapsInjector, which will have the following logic:
- Will take recommendations from the Edge Risk Oracle side and propagate them to the AGRS contract.
- Enforce that only the whitelisted asset can be acted upon.
- Given the protections (percentage constraints and time delay) on the AGRS side and that it is an assumption that risk recommendation will be timing correct updates on the Edge Risk Oracle, the propagation will be permissionless.
The AaveStewardCapsInjector middleware, technically being part of the Aave Robot infrastructure, will run on Chainlink Automation and will be registered using the AaveCLRobotOperator contract with 50 LINK from the Arbitrum Collector.
The new instance of the RiskSteward will be given the RiskAdmin role with the following method: ACL_MANAGER.addRiskAdmin()
Please note that only the following assets on Arbitrum instance have been whitelisted for automatic AGRS system, enforced strictly on the AaveStewardCapsInjector contract: WETH, USDC, USDT, WBTC, DAI, weETH, ARB, USDC.e, GHO, LINK, wstETH, LUSD, FRAX, rETH, AAVE
AGRS
The automated AGRS system will be configured with the following params:
| Parameter | Percent change allowed | minimumDelay |
|---|---|---|
| Supply Cap | 30% (relative change) | 3 days |
| Borrow Cap | 30% (relative change) | 3 days |
Edge Risk Oracle
The methodology used by the Edge Risk Oracle to suggest cap updates is described on the governance forum here.
References
- Implementation: Payload
- Tests: Payload, AaveStewardsInjectorCaps, EdgeRiskStewardCaps
- Snapshot
- Discussion
- AaveStewardsInjectorCaps: github, deployed-contract
- EdgeRiskStewardCaps: github, deployed-contract
- EdgeRiskOracle: github, deployed-contract
Copyright
Copyright and related rights waived via CC0.