a.DI/Governance. Enable support for X Layer
Simple Summary
Proposal to register the necessary X Layer adapters on a.DI, a technical pre-requirement for an activation vote of Aave v3 X Layer.
Motivation
In order to be able to pass messages from Ethereum to X Layer via a.DI (Aave Delivery Infrastructure), it is necessary to at least have one valid adapter Ethereum → X Layer smart contract enabled in the system (native adapter).
The first case of message passing Ethereum → X Layer is the activation proposal for an Aave v3 X Layer pool and consequently, to be able to execute on the X Layer side the payload, the Aave governance should approve in advance the a.DI adapters smart contracts.
Specification
The proposal payload simply registers pre-deployed X Layer adapters (with the necessary configurations to communicate with the X Layer 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 → X Layer path. The required confirmations on the path are 1 out of 1.
| Network | X Layer Native Adapter |
|---|---|
| Ethereum | 0x9fD570da8fFe3384F1093833D44072ea79ABdEB0 |
| X Layer | 0xEbc2c80073E4752e9A1D2e9A9bC98e8F4EeE9Be9 |
The new a.DI deployments on X Layer network are as follows:
| Contract | Address |
|---|---|
| CrossChainController | 0xFdd46155fD3DA5B907AD3B9f9395366290f58097 |
| Granular Guardian | 0xD6727ec503A8d0C10a0EAA4e76eAf9A628188b25 |
The new Aave Governance deployments on X Layer network are as follows:
| Contract | Address |
|---|---|
| PayloadsController | 0x80e11cB895a23C901a990239E5534054C66476B5 |
| Executor Lvl 1 | 0xE2E8Badc5d50f8a6188577B89f50701cDE2D4e19 |
| Governance Guardian | 0xeB55A63bf9993d80c86D47f819B5eC958c7C127B |
| BGD Labs Guardian | 0x734c3fF8DE95c3745770df69053A31FDC92F2526 |