Monad aDI path activation
01Summary
Technical proposal to register three cross-chain message adapters (CCIP, Hyperlane, LayerZero) on Ethereum's Aave Delivery Infrastructure, enabling communication with Monad network. This is a prerequisite for the upcoming Aave v3 Monad pool activation vote. Requires 2 out of 3 adapter confirmations.
- Type
- protocol addition
Key changes
- Enable CCIP adapter for Ethereum-Monad communication (0x7c28CEb47b49cFAC40e718dD407e4249F9C891F6 on Ethereum)(high)
- Enable Hyperlane adapter for Ethereum-Monad communication (0x6bda311748E6542d578b167d791A4130f3FbBc67 on Ethereum)(high)
- Enable LayerZero adapter for Ethereum-Monad communication (0xf9482751C9937fF940b93B5921B8984645dD0a53 on Ethereum)(high)
- Configure 2-of-3 confirmation requirement for Ethereum-Monad message passing(high)
Notable concerns
- This is a technical prerequisite; the actual Aave v3 Monad pool activation will require a separate subsequent vote
- Requires coordination across three different cross-chain messaging protocols
- New Monad network deployments introduce additional smart contracts to the governance system that require monitoring
Generated by Kvorum
02Description
Simple Summary
Proposal to register the necessary Monad adapters on a.DI, a technical pre-requirement for an activation vote of Aave v3 Monad.
Motivation
In order to be able to pass messages from Ethereum to Monad via a.DI (Aave Delivery Infrastructure), it is necessary to have at least one valid adapter Ethereum → Monad smart contract enabled in the system.
The first case of message passing Ethereum → Monad is the activation proposal for an Aave V3 Monad pool, and consequently, to be able to execute on the Monad side the payload, the Aave governance should approve in advance the a.DI adapters smart contracts.
Specification
The proposal payload simply registers pre-deployed Monad adapters (with the necessary configurations to communicate with the Monad 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 → Monad path. The required confirmations on the path are 2 out of 3.
The new a.DI deployments on Monad network are as follows:
| Contract | Address |
|---|---|
| CrossChainController | 0x8dd5b84b26ae3916A5Fb34C8968F93d206216b63 |
| Granular Guardian | 0xD3DD0bE957fcE2dCd359e09374Cbc99f60337D42 |
The new Aave Governance deployments on Monad network are as follows:
| Contract | Address |
|---|---|
| PayloadsController | 0x442CA936e5E6Db875357d0A16481145c96dd9a82 |
| Executor Lvl 1 | 0xa9d0EAFF48cE1DF468f9eAeb7e628c413343F6A2 |
| Governance Guardian | 0x056E4C4E80D1D14a637ccbD0412CDAAEc5B51F4E |
| Aave Labs Guardian | 0x2B99790c35a401be873FA7Eb514D9220736BB1cA |
The Protocol Guardian on Monad is as follows:
| Contract | Address |
|---|---|
| Protocol Guardian | 0xc887455536CBD4e615B745e70CaCde15B3117e74 |
References
- Adapter Implementation:
- Payload Implementation: Payload
- Payload Tests: tests
- Diffs: a.DI diffs
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
A calldata-vs-description analysis is not generated yet. Review the decoded actions →
04Actions
- Target
- 0x5c67…e634
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedMantle a.DI path activation84%
- aaveexecuteda.DI Celo path activation84%
- aaveexecutedMegaEth aDI path activation83%
- aaveexecuteda.DI Sonic path activation83%
- aaveexecutedSoneium aDI path activation82%
- aaveexecutedX Layer network aDI path activation82%
- aaveexecuteda.DI ZkSync path activation81%
- aaveexecutedPlasma aDI path activation81%
- aavecanceledSoneium aDI path activation80%
- aaveexecuteda.DI Linea path activation80%