Mantle a.DI path activation

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.

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

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

References

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

Copyright

Copyright and related rights waived via CC0.