[Direct-to-AIP] Grant Aave Labs RETRY_ROLE on a.DI

Development
1

Simple Summary

This proposal grants the Aave Labs multisig the RETRY_GUARDIAN role on a.DI’s granular access controls.

Recipient: 0x2B99790c35a401be873FA7Eb514D9220736BB1cA

Motivation

a.DI is the cross-chain delivery layer used by Aave governance to route approved governance actions from Ethereum to other networks.

As Aave governance expands across more networks, message delivery operations become more important. The RETRY_ROLE allows a technical operator to retry messages that were already sent through a.DI if a message does not arrive, or to route an already-sent message through another configured bridge adapter if one of the selected providers fails.

Granting this role to Aave Labs improves operational coverage for governance message delivery while keeping control of governance actions with the DAO.

Specification

If approved, this proposal will grant the RETRY_ROLE on a.DI to the Aave Labs multisig:

Aave Labs multisig: 0x2B99790c35a401be873FA7Eb514D9220736BB1cA

The role will be used by Aave Labs as a technical service provider to support retry operations for already-sent a.DI messages when needed.

Next Steps

If consensus is reached, this proposal will move directly to an AIP for onchain execution.

Disclaimer

Aave Labs is presenting this proposal as a service provider to the Aave DAO under the budget approved by the Aave Will Win framework. Aave Labs is contributing this proposal as part of its approved scope of work in support of DAO operations.

Copyright

Copyright and related rights waived via CC0.

2

Greetings Aave community,

This proposal was raised to an AIP. However, the payload has been canceled. We will update this thread when the new AIP Payload is raised.

Aave Labs

3

To complement the initial proposal, Aave Labs would like to make the scope of this update explicit.

The RETRY_ROLE grant is not limited to Ethereum. It applies to every network where a.DI (Aave Delivery Infrastructure) is live: Arbitrum, Avalanche, Base, BNB Chain, Celo, Ethereum, Gnosis, Ink, Linea, Mantle, MegaETH, Metis, Optimism, Plasma, Scroll, Soneium, Sonic, and XLayer. This keeps retry handling consistent across the full delivery layer.

As part of the same update, the guardian of the CrossChainController on Scroll and Metis is transferred from `bgdlabs.eth` to the GranularGuardian. On the remaining a.DI networks the GranularGuardian already holds this role, so this change brings Scroll and Metis in line with the default a.DI configuration and keeps guardian roles administered uniformly across all networks.