Aave

Simple Summary

Proposal to update emergency roles (protocol & governance) to the new elected Aave Protocol & Emergency Guardians.

Motivation

This year, the community decided to renew the Aave Guardian and making it more granular with a Protocol Emergency Guardian and a Governance Emergency Guardian. Even if new pieces of infrastructure (e.g. Lido/Etherfi/zkSync) pools have been configured with the new Guardians on activation stage, it is still necessary to update via governance proposal different on-chain roles, from old guardians to new ones.

Specification

• Protocol Guardian
  • For Aave v2 pools POOL_ADDRESS_PROVIDER.setEmergencyAdmin() is called to replace the old Guardian with the new one.
  • For Aave v3 ACL_MANAGER.addEmergencyAdmin() is called to give the role to the new Guardian and ACL_MANAGER.removeEmergencyAdmin() to remove it from the old Guardian. This is not necessary for new pools where the new Guardian is already configured: zkSync, Lido, Etherfi.

The list of Protocol Guardian Safes is the following:

The list of Governance Guardian Safes is the following:

References

• Permissions diff
• Implementation: AaveV2Ethereum, AaveV2EthereumAMM, AaveV2Polygon, AaveV2Avalanche, AaveV3Ethereum, AaveV3Polygon, AaveV3Avalanche, AaveV3Optimism, AaveV3Arbitrum, AaveV3Metis, AaveV3Base, AaveV3Gnosis, AaveV3Scroll, AaveV3BNB
• Tests: AaveV2Ethereum, AaveV2EthereumAMM, AaveV2Polygon, AaveV2Avalanche, AaveV3Ethereum, AaveV3Polygon, AaveV3Avalanche, AaveV3Optimism, AaveV3Arbitrum, AaveV3Metis, AaveV3Base, AaveV3Gnosis, AaveV3Scroll, AaveV3BNB
• Discussion

Copyright

Copyright and related rights waived via CC0.