[AAVE] Mantle a.DI path activation

Voting ended 11 months agoSucceeded

Simple Summary

Proposal to activate the necessary a.DI and governance infrastructure for the Mantle network, a technical prerequisite for an activation vote of Aave v3 Mantle.

Motivation

In order to be able to pass messages from Ethereum to Mantle via a.DI (Aave Delivery Infrastructure), it is necessary to at least have three valid adapters Ethereum → Mantle smart contracts enabled in the system.

The first case of message passing Ethereum → Mantle is the activation proposal for an Aave v3 Mantle pool, and consequently, to be able to execute on the Mantle side the payload, the Aave governance should approve in advance the a.DI adapters smart contracts.

This procedure mirrors the requirements of previous networks like ZkSync or Linea.

Specification

The proposal payload simply registers pre-deployed Mantle adapters (with the necessary configurations to communicate with the Mantle a.DI) on the Ethereum a.DI instance.

This is done by calling the enableBridgeAdapters() function on the Ethereum Cross-chain Controller smart contract.

The following are the configured adapters for the Ethereum → Mantle path. The required confirmations on the path are 1 out of 1.

| Network | Mantle Native Adapter | |

--
Ethereum
Mantle

The new a.DI deployments on Mantle network are as follows:

| Contract | Address | |

--
CrossChainController
Granular Guardian

The new Aave Governance deployments on Mantle network are as follows:

| Contract | Address | |

| -- | | PayloadsController | 0xF089f77173A3009A98c45f49D547BF714A7B1e01 | | Executor Lvl 1 | 0x70884634D0098782592111A2A6B8d223be31CB7b | | Governance Guardian | 0x14816fC7f443A9C834d30eeA64daD20C4f56fBCD | | BGD Labs Guardian | 0x0686f59Cc2aEc1ccf891472Dc6C89bB747F6a4A7 |

References

Adapter Implementations: Mantle Native Adapters
Payload Implementation: Payload
Payload Tests: tests
Diffs: a.DI diffs
Snapshot: Direct-to-AIP
Discussion

Copyright

https://app.aave.com/governance/v3/proposal/?proposalId=294

Off-Chain Vote

YAE

180 HVAXVC99.4%

NAY

1 HVAXVC0.6%

Quorum:18100%

Download mobile app to vote

Discussion

[AAVE] Mantle a.DI path activation

Timeline

Apr 15, 2025Proposal created

Apr 16, 2025Proposal vote started

Apr 18, 2025Proposal vote ended

Mar 26, 2026Proposal updated

Motivation

This procedure mirrors the requirements of previous networks like ZkSync or Linea.

Specification

The proposal payload simply registers pre-deployed Mantle adapters (with the necessary configurations to communicate with the Mantle a.DI) on the Ethereum a.DI instance.

This is done by calling the enableBridgeAdapters() function on the Ethereum Cross-chain Controller smart contract.

The following are the configured adapters for the Ethereum → Mantle path. The required confirmations on the path are 1 out of 1.

| Network | Mantle Native Adapter | |

Ethereum

Mantle

The new a.DI deployments on Mantle network are as follows:

| Contract | Address | |

CrossChainController

Granular Guardian

The new Aave Governance deployments on Mantle network are as follows:

| Contract | Address | |