a.DI Sonic path activation
01Summary
Register three Sonic bridge adapters (Hyperlane, LayerZero, CCIP) on Ethereum's Aave Delivery Infrastructure to enable cross-chain message passing from Ethereum to Sonic, a technical prerequisite for the upcoming Aave v3 Sonic pool activation vote.
- Type
- protocol addition
Key changes
- Enable three bridge adapters (Hyperlane, LayerZero, CCIP) on Ethereum Cross-chain Controller for Ethereum → Sonic message passing(high)
- Register corresponding adapter deployments on Sonic network (CrossChainController, Granular Guardian, Chainlink Emergency Oracle)(high)
- Deploy Aave Governance contracts on Sonic (PayloadsController, Executor Lvl 1, Governance Guardian, BGD Labs Guardian)(high)
- Set optimal bandwidth for Ethereum → Sonic path to 2 via updateOptimalBandwidthByChain()(medium)
- Configure required confirmations for Ethereum → Sonic path as 2 out of 3 adapters(high)
Notable concerns
- This is a technical maintenance proposal with no independent risk analysis provided in the material
- Requires 2 out of 3 adapter confirmations for message passing, introducing dependency on bridge infrastructure reliability
- Mirrors previous network implementations (ZkSync, Linea, Celo) but Sonic-specific testing and audits are referenced in external links only
Generated by Kvorum
02Description
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.
| Network | Hyperlane Adapter | LayerZero Adapter | CCIP Adapter |
|---|---|---|---|
| Ethereum | 0x01dcb90Cf13b82Cde4A0BAcC655585a83Af3cCC1 | 0x8FD7D8dd557817966181F584f2abB53549B4ABbe | 0xe3a0d9754aD3452D687cf580Ba3674c2D7D2f7AE |
| Sonic | 0x1098F187F5f444Bc1c77cD9beE99e8d460347F5F | 0x7B8FaC105A7a85f02C3f31559d2ee7313BDC5d7f | 0x1905fCdDa41241C0871A5eC3f9dcC3E8d247261D |
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:
| Contract | Address |
|---|---|
| PayloadsController | 0x0846C28Dd54DEA4Fd7Fb31bcc5EB81673D68c695 |
| Executor Lvl 1 | 0x7b62461a3570c6AC8a9f8330421576e417B71EE7 |
| Governance Guardian | 0x63C4422D6cc849549daeb600B7EcE52bD18fAd7f |
| BGD Labs Guardian | 0x7837d7a167732aE41627A3B829871d9e32e2e7f2 |
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.
03Mismatch analysis
placeholder
Generated by Kvorum
04Actions
- Target
- 0x41fe…035e
- 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
- aaveexecutedSoneium aDI path activation86%
- aaveexecuteda.DI Celo path activation84%
- aavecanceledSoneium aDI path activation84%
- aaveexecutedMonad aDI path activation83%
- aaveexecuteda.DI ZkSync path activation83%
- aaveexecutedPlasma aDI path activation83%
- aaveexecutedX Layer network aDI path activation81%
- aaveexecutedMegaEth aDI path activation81%
- aaveexecuteda.DI Linea path activation80%
- aaveexecutedBob Network aDI path activation79%