KVORUM
aaveSource: Aave governance v3 · #312

Soneium aDI path activation

executedMay 19, 2025, 06:49 AM UTCbyF70xf71f…1e02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Technical governance proposal to register Soneium adapters on Aave Delivery Infrastructure (a.DI), enabling message passing from Ethereum to Soneium. This is a prerequisite for the upcoming Aave v3 Soneium pool activation vote. The proposal configures pre-deployed native adapters with 1-of-1 confirmation requirements.

Type
protocol addition

Key changes

  • Register Soneium native adapter (0xe66973c4571F733CafEb1BDE1fa58Ff35416d901) on Ethereum a.DI via enableBridgeAdapters() function on Cross-chain Controller(high)
  • Enable Ethereum to Soneium message passing with 1-of-1 confirmation requirement(high)
  • Deploy a.DI infrastructure on Soneium including CrossChainController and Granular Guardian(medium)
  • Deploy Aave Governance infrastructure on Soneium including PayloadsController, Executor Lvl 1, Governance Guardian, and BGD Labs Guardian(medium)

Notable concerns

  • This is a technical prerequisite that must pass before the Aave v3 Soneium pool activation proposal can be executed
Contracts0xd934a9034c95f9c31e1d6077dfed49b0f4d36fc30xe66973c4571F733CafEb1BDE1fa58Ff35416d9010xD92b37a5114b33F668D274Fb48f23b726a854d6E0xD8E6956718784B914740267b7A50B952fb5166560x44D73D7C4b2f98F426Bf8B5e87628d9eE38ef0Cf0x47aAdaAE1F05C978E6aBb7568d11B7F6e0FC4d6A0x19CE4363FEA478Aa04B9EA2937cc5A2cbcD44be60xdc62E0e65b2251Dc66404ca717FD32dcC365Be3A
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

315 words

Simple Summary

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

Motivation

In order to be able to pass messages from Ethereum to Soneium via a.DI (Aave Delivery Infrastructure), it is necessary to at least have one valid adapter Ethereum → Soneium smart contract enabled in the system (native adapter).

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

Specification

The proposal payload simply registers pre-deployed Soneium adapters (with the necessary configurations to communicate with the Soneium 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 → Soneium path. The required confirmations on the path are 1 out of 1.

NetworkSoneium Native Adapter
Ethereum0xe66973c4571F733CafEb1BDE1fa58Ff35416d901
Soneium0x5698e43Ef1be85C68Dec568B5925dD5DB7903e39

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

ContractAddress
CrossChainController0xD92b37a5114b33F668D274Fb48f23b726a854d6E
Granular Guardian0xD8E6956718784B914740267b7A50B952fb516656

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

ContractAddress
PayloadsController0x44D73D7C4b2f98F426Bf8B5e87628d9eE38ef0Cf
Executor Lvl 10x47aAdaAE1F05C978E6aBb7568d11B7F6e0FC4d6A
Governance Guardian0x19CE4363FEA478Aa04B9EA2937cc5A2cbcD44be6
BGD Labs Guardian0xdc62E0e65b2251Dc66404ca717FD32dcC365Be3A

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal follows the standard Aave governance payload pattern: the single decoded on-chain action is a generic execute() call to a payload contract address (0xd934a9034c95f9c31e1d6077dfed49b0f4d36fc3). This is consistent with how Aave AIPs are structured — the top-level proposal action delegatecalls into a payload contract that internally performs the specific logic (here, calling enableBridgeAdapters() on the Ethereum Cross-chain Controller to register the Soneium adapter). However, the decoded calldata provided does not expose the internal call details (target Cross-chain Controller address, adapter addresses, confirmation counts), so I cannot directly verify that the specific parameters described (adapter addresses, 1-of-1 confirmations) match what the payload executes. Nothing in the visible calldata contradicts the description, and the overall pattern (single execute() call bootstrapping a technical/administrative change) is exactly what one would expect for this type of proposal. Given the lack of visibility into the payload's internal logic, I cannot fully confirm the specific technical details, so confidence is low, but there is no evidence of any discrepancy between the description and what is decoded.,

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0fallback()chain 0x1
Target
0xd934…6fc3
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.