Simple Summary

Proposal to register the necessary Ink adapters on a.DI, a technical pre-requirement to have Aave Governance-controlled contracts on Ink, in this case, cross-chain GHO-related to be listed on the Aave <> Ink friendly fork.

Motivation

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

The first case of message passing Ethereum → Ink is the proposal for GHO CCIP configuration on Ink, and consequently, to be able to execute on the Ink side the payload, the Aave governance should approve in advance the a.DI adapters smart contracts.

This procedure mirrors the requirements of previous networks like Base or Optimism.

Specification

The proposal payload simply registers pre-deployed Ink adapters (with the necessary configurations to communicate with the Ink 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 → Ink path. The required confirmations on the path are 1 out of 1.

The new a.DI deployments on Ink network are as follows:

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

References

• Adapter Implementations: Ink Native Adapters
• Payload Implementation: Payload
• Payload Tests: tests
• Diffs: a.DI diffs
• Snapshot: Direct-to-AIP
• Discussion

Copyright

Copyright and related rights waived via CC0.