Technical maintenance proposals

a.DI/Governance. Enable support for Sonic


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

To pass messages from Ethereum to Sonic via a.DI (Aave Delivery Infrastructure), it is necessary to have at least 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 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:

Contract Address
CrossChainController 0x58e003a3C6f2Aeed6a2a6Bc77B504566523cb15c
Granular Guardian 0x10078c1D8E46dd1ed5D8df2C42d5ABb969b11566
Chainlink Emergency Oracle 0xECB564e91f620fBFb59d0C4A41d7f10aDb0D1934

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