← Back to Aave
Aave · closed proposal

# Sync emergency admin on v2 AMM

0xf71f…1e02·ended 57y ago·LOW RISK
Voters
11
AAVE voted
563394931391835.13B
≈$35127673972280924.00B
Token price
$62.35

AI summary

This proposal aims to update the 'emergency admin' address for the Aave v2 AMM pool. The current emergency admin is an outdated address, and this proposal seeks to align it with the Aave Guardian address used across other Aave instances like Aave v2 and v3 Ethereum. This change is for consistency and operational hygiene, even though the v2 AMM pool is deprecated and largely unused.

Impact

If this proposal passes, the emergency admin for the Aave v2 AMM pool will be updated to the correct Aave Guardian address. This improves the security posture and consistency across Aave's systems, benefiting the overall protocol and its users by ensuring proper emergency response capabilities, even for a deprecated pool. No specific group loses out.

Read full proposal on Tally

Voting results

For563394931391835.13B (100.0%)
Against0 (0.0%)
Abstain0 (0.0%)
563394931391835.13B AAVE · ≈$35127673972280924.00B · 11 votersblock 2023-12-12T10:40:59Z

🐳 Whale votes

0 votes > 5% VP
No whale votes on this proposal.

Full proposal

Original markdown · Aave

Sync emergency admin on v2 AMM


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, f…

📚 Similar past proposals

Finding similar proposals…