KVORUM
aaveSource: Aave governance v3 · #232

a.DI Celo path activation

executedJan 18, 2025, 06:28 PM UTCbyF70xf71f…1e02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Enable three bridge adapters (Hyperlane, LayerZero, and CCIP) on Ethereum's a.DI (Aave Delivery Infrastructure) to support cross-chain messaging from Ethereum to Celo, a technical prerequisite for activating Aave v3 on Celo.

Type
protocol addition

Key changes

  • Register Hyperlane adapter (0x01dcb90Cf13b82Cde4A0BAcC655585a83Af3cCC1) on Ethereum a.DI for Celo communication(high)
  • Register LayerZero adapter (0x8410d9BD353b420ebA8C48ff1B0518426C280FCC) on Ethereum a.DI for Celo communication(high)
  • Register CCIP adapter (0x58489B249BfBCF5ef4B30bdE2792086e83122B6f) on Ethereum a.DI for Celo communication(high)
  • Enable cross-chain messaging infrastructure from Ethereum to Celo network(high)

Notable concerns

  • This is a technical prerequisite that must be approved before the subsequent activation proposal for Aave v3 on Celo can be executed
  • Requires coordination with pre-deployed adapter contracts on both Ethereum and Celo networks
Contracts0x8f7e2023686b78e148e65004ca8acef9b2b469220x01dcb90Cf13b82Cde4A0BAcC655585a83Af3cCC10x8410d9BD353b420ebA8C48ff1B0518426C280FCC0x58489B249BfBCF5ef4B30bdE2792086e83122B6f
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

320 words

Simple Summary

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

Motivation

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

The first case of message passing Ethereum → Celo is the activation proposal for an Aave v3 Celo pool and consequently, to be able to execute on the Celo 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 Scroll or ZkSync.

Specification

The proposal payload simply registers pre-deployed Celo adapters (with the necessary configurations to communicate with the Celo a.DI) on the Ethereum a.DI instance.

This is done by calling the enableBridgeAdapters() function on the Ethereum Cross-chain Controller smart contract.

NetworkHyperlane AdapterLayerZero AdapterCCIP Adapter
Ethereum0x01dcb90Cf13b82Cde4A0BAcC655585a83Af3cCC10x8410d9BD353b420ebA8C48ff1B0518426C280FCC0x58489B249BfBCF5ef4B30bdE2792086e83122B6f
Celo0x7b065E68E70f346B18636Ab86779980287ec73e00x83BC62fbeA15B7Bfe11e8eEE57997afA5451f38C0x3d534E8964e7aAcfc702751cc9A2BB6A9fe7d928

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

ContractAddress
CrossChainController0x50F4dAA86F3c747ce15C3C38bD0383200B61d6Dd
Granular Guardian0xbE815420A63A413BB8D508d8022C0FF150Ea7C39
Chainlink Emergency Oracle0x91b21900E91CD302EBeD05E45D8f270ddAED944d

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

ContractAddress
PayloadsController0xE48E10834C04E394A04BF22a565D063D40b9FA42
Executor Lvl 10x1dF462e2712496373A347f8ad10802a5E95f053D
Governance Guardian0x056E4C4E80D1D14a637ccbD0412CDAAEc5B51F4E
BGD Labs Guardian0xfD3a6E65e470a7D7D730FFD5D36a9354E8F9F4Ea

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

1 total
#0fallback()chain 0x1
Target
0x8f7e…6922
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.