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:

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

The Protocol Guardian on Monad is as follows:

References

• Adapter Implementation:
  • CCIPAdapter
  • HyperLaneAdapter
  • LayerZeroAdapter
• Payload Implementation: Payload
• Payload Tests: tests
• Diffs: a.DI diffs
• Discussion

Copyright

Copyright and related rights waived via CC0.