Executed

Sync emergency admin on v2 AMM


Proposal ID

401

Proposed

Dec 12th, 2023

Result details
Final Votes

Quorum

563.39K of 0

Majority support

Yes

For

563.39K

Against

0

Abstain

0

Actions

Function 1:

0x00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000dabad81af85554e9ae636395611c58f7ec1aaec50000000000000000000000000000000000000000000000000000000000000023
Value:0

Proposal


title: "Sync emergency admin on v2 AMM" author: "BGD Labs (@bgdlabs)" discussions: "https://governance.aave.com/t/bgd-technical-maintenance-proposals/15274/10"

Simple Summary

This proposal aligns the emergency admin address on the deprecated Aave v2 AMM pool with the one of Aave v2 and v3 Ethereum.

Motivation

During an internal security review procedure of Aave, we detected that the emergency admin on Aave v2 AMM is a legacy address, not aligned with the Aave Guardian.

Even if the v2 AMM pool is deprecated (frozen) and almost off-boarded, for hygiene we think it is appropriate to have consistency on all Aave instances in the same network, and simpler for operations.

Specification

Upon execution, the proposal will call setEmergencyAdmin(0xCA76Ebd8617a03126B6FB84F9b1c1A0fB71C2633) on the addresses provider contract of v2 AMM, passing the address of the Aave Ethereum Guardian.

References

Copyright

Copyright and related rights waived via CC0.

Final Votes

Quorum

563.39K of 0

Majority support

Yes

For

563.39K

Against

0

Abstain

0

Final Votes
Status

Tue Dec 12, 10:40 am

Published onchain

Tue Dec 19, 03:09 am

Voting period started

Thu Dec 21, 07:09 pm

Voting period ended

Sun Dec 17, 03:31 am

Proposal executed