Simple Summary

Proposal to register the necessary Celo adapters on a.DI, a technical pre-requirement for an activation vote of Aave v3 Celo.

Motivation

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

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

This procedure mirrors the requirements on previous networks like Scroll or ZkSync.

Specification

The proposal payload simply registers pre-deployed Celo adapters (with the necessary configurations to communicate with the Celo 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 new a.DI deployments on Linea network are as follows:

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

References

• Adapter Implementations: HyperLane Bridge Adapters, LayerZero Bridge Adapters, CCIP Bridge Adapters
• Payload Implementation: Payload
• Payload Tests: tests
• Diffs: a.DI diffs
• Snapshot: Direct-to-AIP
• Discussion

Copyright

Copyright and related rights waived via CC0.