FeedProjects
Developers
Settings
🎉 A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
Aave

Insights

Proposals

Discussions

Members

Information

Reports

Create Proposal

Aave

InsightsProposalsDiscussionsMembersInformationReports
Proposal
Back to Proposals
executedEnds a year ago ·  Onchain

a.DI Sonic path activation

By 0xf71f...c61E02

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.

NetworkHyperlane AdapterLayerZero AdapterCCIP Adapter
Ethereum0x01dcb90Cf13b82Cde4A0BAcC655585a83Af3cCC10x8FD7D8dd557817966181F584f2abB53549B4ABbe0xe3a0d9754aD3452D687cf580Ba3674c2D7D2f7AE
Sonic0x1098F187F5f444Bc1c77cD9beE99e8d460347F5F0x7B8FaC105A7a85f02C3f31559d2ee7313BDC5d7f0x1905fCdDa41241C0871A5eC3f9dcC3E8d247261D

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

ContractAddress
CrossChainController0x58e003a3C6f2Aeed6a2a6Bc77B504566523cb15c
Granular Guardian0x10078c1D8E46dd1ed5D8df2C42d5ABb969b11566
Chainlink Emergency Oracle0xECB564e91f620fBFb59d0C4A41d7f10aDb0D1934

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

ContractAddress
PayloadsController0x0846C28Dd54DEA4Fd7Fb31bcc5EB81673D68c695
Executor Lvl 10x7b62461a3570c6AC8a9f8330421576e417B71EE7
Governance Guardian0x63C4422D6cc849549daeb600B7EcE52bD18fAd7f
BGD Labs Guardian0x7837d7a167732aE41627A3B829871d9e32e2e7f2

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.

Continue Reading
Connect Wallet to Add Note
0
Never Miss a ProposalSign up for Aave notifications
Cast Vote
Votes 22
VoterCast PowerVote & Rationale
0x57ab...112922
287,113

YAE

EzR3aL
117,044

YAE

TokenLogic
46,791

YAE

StableLab
43,339

YAE

0x3DDC...8A05B0
30,002

YAE

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Wed February 12 2025, 06:40 pmPublished Onchain 0xf71f...c61E02
  • Thu February 13 2025, 06:40 pmVoting Period Starts
  • Sun February 16 2025, 06:40 pmEnd Voting Period
  • Sun February 16 2025, 07:20 pmQueue Proposal
  • Sun February 16 2025, 07:21 pmExecute Proposal
Current Results

1-YAE

559,115.06

2-NAY

N/A Tokens

0%
Quorum 559,115.06/320,000
DocumentationBrandingContact Us
Press space bar to start a drag. When dragging you can use the arrow keys to move the item around and escape to cancel. Some screen readers may require you to be in focus mode or to use your pass through key