Simple Summary

Proposal to register the necessary Sonic adapters on a.DI, a technical pre-requirement for an activation vote of Aave v3 Sonic.

Motivation

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

The first case of message passing Ethereum → Sonic is the activation proposal for an Aave v3 Sonic pool and consequently, to be able to execute on the Sonic side the payload, the Aave governance should approve in advance the a.DI adapters smart contracts.

This procedure mirrors the requirements on previous networks like ZkSync, Linea, or Celo.

Specification

The proposal payload simply registers pre-deployed Sonic adapters (with the necessary configurations to communicate with the Sonic 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 optimal bandwidth on the Ethereum -> Sonic path is set to 2, by calling updateOptimalBandwidthByChain().

The following are the configured adapters for the Ethereum → Sonic path. The required confirmations on the path are 2 out of 3.

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

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

References

• Adapter Implementations: HyperLane Bridge Adapters, LayerZero Bridge Adapters, CCIP Bridge Adapters
• Payload Implementation: Payload
• Payload Tests: tests
• Diffs: a.DI diffs
• Snapshot: Direct-to-AIP
• Discussion

Copyright

Copyright and related rights waived via CC0.