KVORUM
aaveSource: Aave governance v3 · #433

Upgrade Aave instances to v3.6 Part 2

executedJan 15, 2026, 02:29 PM UTCbyF70xf71f…1e02

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

178 words

Simple Summary

Upgrade the Aave protocol instances from v3.5 to v3.6 Part 2.

Motivation

Aave v3.6 enhances isolation, via more fine-grained configurations and the decoupling of eMode and eMode0 settings. For a comprehensive overview of the changes, please refer to the documentation.

Specification

The upgrade payload updates the implementations of the Pool, PoolConfigurator, AToken & VariableDebtToken on the second set of pools, namely Mainnet(Core), Mainnet(Prime), Plasma, Base, Arbitrum, Avalanche, Linea, BNB Chain, Polygon.

On mainnet core the payloads varies slightly to account for:

  • aAave which has a different implementation due to the governance delegation integration
  • vGHO which has a different implementation due to the deprecated discount mechanism on stkAAVE

Security procedures

The upgrade was extensively unit tested and fuzzed. Certora adapted its formal properties to ensure the upgrade's correctness. In addition 5 audits by Independent Auditors were conducted.

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

2 total
#0fallback()chain 0x1
Target
0x95d6…1b6f
Value
0 wei
Function
fallback()
Arguments
{}
Calldata
#0fallback()chain 0x1
Target
0xacae…d44d
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.