Update: Risk Council Transition
Following our April 7th statement, we want to update the community on the concrete steps we have taken to ensure the continuity of Aave’s risk management.
Multisig Ownership Transfer
Per our instructions and with the support of Aave Labs, @ChaosLabs, and @bgdlabs have gracefully transitioned ownership of the Risk Council multisigs. The signers are now:
- @AaveLabs:
0x606dC57cd166643760E049609bfd1D8a698D3bAc - @LlamaRisk:
0xbA037E4746ff58c55dc8F27a328C428F258DDACb
With a threshold of 2/2.
The change was executed across Aave instances, as detailed below:
| Network | Status | Transaction Hash |
|---|---|---|
| Arbitrum |  Transferred |
0x8980…d28b |
| Avalanche | Transferred |
0x4ec5…35d8 |
| Base | Transferred |
0xa6c2…ba86 |
| BNB Chain | Transferred |
0xf398…3e3e |
| Celo | Transferred |
0xf4be…8055 |
| Gnosis | Transferred |
0x4e1b…8ed8 |
| Ink | Not applicable (whitelabel instance) | |
| Linea | Transferred |
0xd841…b8d8 |
| Mainnet (Core, Prime, EtherFi) | Transferred |
0x24c5…bce2 |
| Mantle | Transferred |
0x5a10…567c |
| MegaEth | Transferred |
0xa3ba…6bdd |
| Metis | Not applicable (deprecated market) | |
| Optimism | Transferred |
0x60c7…c3ec |
| Plasma | Transferred |
0x0e9e…a556 |
| Polygon | Transferred |
0xfe8b…4747 |
| Scroll | Transferred |
0x0805…906e |
| Soneium | Not applicable (deprecated market) | |
| Sonic | Transferred |
0x946c…d98c |
| X Layer | Transferred |
0xe945…4d9b |
| ZkSync | Transferred |
0x269f…ad70 |
Risk Oracle Discontinuation
We have confirmed that Chaos Labs has discontinued its Risk Oracles, with no updates published since April 8th. As a precautionary measure, we will prepare an ARFC to discontinue the on-chain access previously granted to their Risk Oracles.
Operational Continuity
We have already begun exercising the Risk Steward function. Our first update was increasing the supply cap for PT-sUSDE-18JUN2026 on the Plasma instance, which was urgently needed. We are preparing additional Risk Steward updates based on the parameter changes we have identified.
Functions previously handled via automated Risk Oracles will be managed manually through our quantitative methodology and monitoring infrastructure, using the established channels: Risk Steward, ARFC, and DAIP. This covers all departing automated functions, including CAPO snapshots and PT oracle parametrization, which we are actively addressing.
We have full monitoring in place, a comprehensive methodology covering all asset parameters, and we will submit parameter changes in a timely manner via the appropriate channel as conditions require.
Next Steps
We will keep the community updated on our progress toward CRE-based Risk Oracles, as outlined in our previous posts.