# Technical maintenance proposals

**URL:** <https://governance.aave.com/t/technical-maintenance-proposals/15274>\
**Category:** Development\
**Created:** [October 30, 2023, 3:04pm UTC](https://governance.aave.com/t/technical-maintenance-proposals/15274 "2023-10-30T15:04:01Z")\
**Posts on this page:** 1\
**Showing post:** 75

<div class="post-metadata">

**Author:** ![bgdlabs](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/bgdlabs/32/1829_2.png) [@bgdlabs](https://governance.aave.com/u/bgdlabs)\
**Post date:** [April 7, 2025, 7:11am UTC](https://governance.aave.com/t/technical-maintenance-proposals/15274/75 "2025-04-07T07:11:21Z")

</div>

## POOL\_ADMIN renounceRole() by Guardian on new pools

### Simple Summary

After some maturity, it is perfectly safe for the Aave Guardian to renounce the `POOL_ADMIN` role in relatively new pools: **Linea, Sonic**.

### Motivation

Whenever Aave expands to a new network, it does so fully decentralised via an on-chain governance proposal (e.g., [Aave v3 Sonic](https://vote.onaave.com/proposal/?proposalId=257)).  
Major permissions (upgradeability) of the pool are set to the Aave governance from day 0, but the `POOL_ADMIN` is given to the Aave Guardian during a period for security.

From a technical/security perspective, we don’t see any risk at the moment or need for the Guardian to hold this role anymore on the aforementioned networks: all apart from Celo, as this last one has undergone a network infrastructure migration only slightly more than 1 week ago.

### Specification

_This proposal doesn’t require any governance procedure (Snapshot, on-chain), as the renounce is done directly by the Guardian._

Each instance of the Aave Guardian (Safe) will call the `renounceRole()` function for the `POOL_ADMIN` role and its address.

---

_[View the full topic](https://governance.aave.com/t/technical-maintenance-proposals/15274)._