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