As we prepare the AIP to deploy CAPO Risk Oracles into the protocol via Chaos Risk Agents, we’d like to share an update with the community on our initial launch phase and the accompanying on-chain constraint updates.
In the initial phase, we will enable CAPO automation on the Ethereum network. The following PriceCapAdapter oracles will be whitelisted:
| Asset/Price Cap Adapter |
|---|
| wstETH |
| weETH |
| rsETH |
| osETH |
| ezETH |
| cbETH |
| rETH |
| tETH |
| ETHx |
| LBTC |
| eBTC |
| sUSDe |
| syrupUSDT |
| sDAI |
The CAPO Risk Agent update struct introduces a merged timelock for both snapshotRatio and maxYearlyRatioGrowthPercent. In other words, these parameters will be updated together, rather than using separate update paths per-parameter.
Given this coupling, we aim to:
- Align the
snapshotRatiotimelock to match the existingmaxYearlyRatioGrowthPercenttimelock of 3 days - Tighten
snapshotRatio’s per-update bound by lowering maxRelativeChange to 3% (from 5%) to reflect the fact that updates are now coupled
| Parameter | Max Relative Change per Update | Timelock |
|---|---|---|
snapshotRatio |
3% | 3 Days |
maxYearlyRatioGrowthPercent |
10% | 3 Days |