KVORUM
aaveSource: Aave governor v2 · #127

Aave StarkNet Phase I - Aave <> StarkNet Bridge deployment/activation by Aave governance

executedDec 4, 2022, 03:34 AM UTCbyB80xb85f…8a7c

01Summary

AISummary by Kvorumclaude-haiku-4-5

This governance proposal deploys and activates smart contract components for bridging Aave v2 Ethereum aTokens (aUSDC, aUSDT, aDAI) to StarkNet, with a 30,000 unit ceiling per asset. The deployment includes a Bridge contract on Ethereum, cross-chain messaging via StarkNet core contracts, and activation of L2 components including rewAAVE and L2 aToken versions.

Type
protocol addition

Key changes

  • Deploy and initialize Bridge contract on Ethereum to enable aToken bridging to StarkNet(high)
  • Set bridging ceilings of 30,000 units each for aUSDC, aUSDT, and aDAI(high)
  • Activate Governance Relay and L2 bridge components on StarkNet via cross-chain messaging(high)
  • Activate rewAAVE (AAVE rewards representation) on StarkNet(medium)
  • Connect L1 Bridge to L2 bridge infrastructure and L1 aTokens to L2 static versions(high)
Contracts0x25c0667E46a704AfCF5305B0A586CC24c171E94D0x07bbb769e53d886f77792d59b9cd65a2eb14a84c49a0942ba9577e291deefcec0x00be3e7fe64939ef463bc80b76703b93c10a61944de34df5bb2dbc7b734e3159
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

373 words

Simple Summary

This governance proposal deploys and activates the different smart contract components result of the community project to create a bridge of Aave v2 Ethereum aTokens from/to StarkNet.

Motivation

All the information regarding the project is explained on https://governance.aave.com/t/aave-starknet-phase-i-release/10428.

In summary, with the previous approval of the project via governance, the Aave community has decided to start its expansion to StarkNet, a validity rollup, starting with smart contracts for bridging infrastructure of Aave v2 Ethereum aTokens.

Additionally, this also sets the foundation for the connection of instances of Aave in other networks (e.g. Polygon, Avalanche) with StarkNet.

Specification

This proposal's payload does the following:

Ethereum side

  1. Deploys the Bridge smart contract, main component on Ethereum of the system, by calling a transparent proxy factory.
  2. Initializes the Ethereum Bridge to accept bridging of aUSDC, aUSDT and aDAI, with a 30'000 total ceiling for each one of them (in units of each asset, which in this case is relatively equivalent to USD).
  3. Sends a message via the StarkNet core messaging smart contract to activate the smart contract components on the StarkNet side.

StarkNet side

  1. The message is received by the Governance Relay contract (proxy HERE and implementation HERE), which executes the payload on https://starkscan.co/class/0x00be3e7fe64939ef463bc80b76703b93c10a61944de34df5bb2dbc7b734e3159#code via delegatecall.
  2. The payload connects and activates all the components: activates rewAAVE (representing AAVE rewards on StarkNet), connects the L1 Bridge to the L2 side of it, and connects the L1 aTokens to their static versions on L2.

The payload smart contract for Ethereum can be found HERE,

The payload smart contract for StarkNet can be found HERE.

All the other components are also present in the same repository.

After this proposal gets approved and executed, the Bridge will be fully operative on https://etherscan.io/address/0x25c0667E46a704AfCF5305B0A586CC24c171E94D (no code at the moment, being a counterfactual/CREATE2 deployment).

Security procedures

This proposal has been tested using the available tools to be as close as possible to fork both Ethereum and StarkNet mainnets.

In addition, all the components apart from the payload had gone through the security procedures enumerated on the Aave governance forum HERE.

Bored Ghost Developing has reviewed the proposal payload too.

Deployed Contracts

https://github.com/aave-starknet-project/aave-starknet-bridge#deployed-contracts

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The proposal executes exactly one on-chain action: a call to execute() on a dedicated payload contract (0x4919e176...). This is the standard Aave governance pattern where a single payload contract encapsulates multiple internal steps (deploying the Bridge via proxy factory, initializing asset ceilings, and sending the StarkNet message) that are not individually visible in the top-level decoded calldata but are documented and linked in the description itself, including a link to the payload contract's source code and confirmation it was reviewed by BGD Labs. Since the description explicitly identifies this exact payload address and explains that it performs the itemized steps, and since Aave governance proposals routinely delegate multi-step logic to a single payload executor, I cannot flag omissions of the constituent operations (Bridge deployment, ceiling initialization, StarkNet messaging) as discrepancies — they are implemented inside the single decoded call rather than as separate top-level actions, consistent with normal proposal execution patterns. There is no value, target, or direction mismatch between what is decoded (a call to the specified payload contract) and what the description claims that payload does. Confidence is medium rather than high because the internal logic of the payload contract itself is not independently decoded here, so I cannot verify at the calldata level that the ceilings are exactly 30,000 or that the StarkNet activation logic matches precisely — this reflects the limits of visibility into a single opaque execute() call rather than an actual detected mismatch.excerpt

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
0x4919…d026
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.