Aave contract 0xf6d2…ab18 on Ethereum

0xf6d2224916ddfbbab6e6bd0d1b7034f4ae0cab18

As of 21 Nov 2026, Trustblock’s record holds 0xf6d2224916ddfbbab6e6bd0d1b7034f4ae0cab18 on Ethereum as a contract of Aave. No audit report on Trustblock names this address in its stored scope. Aave has 45 audit reports on Trustblock, the newest from Certora, 30 Jun 2026.

Aave audit reports on Trustblock45

None of them names this address in its stored scope. The newest 10 are listed here.

AuditSecurity firmDateCommit named in the reportReport
Aave StableVaultCertoraNot recorded (see the report)Open
Aave V4 Tokenization SpokeCertoraNot recorded (see the report)Open
AaveMixBytesNot recorded (see the report)Open
Aave V4 HubCertoraNot recorded (see the report)Open
Aave V4 SpokeCertoraNot recorded (see the report)Open
Aave V4 LibrariesCertoraNot recorded (see the report)Open
Aave V4 Tokenization SpokeChainSecurityNot recorded (see the report)Open
Aave Labs auditSherlockNot recorded (see the report)Open
Aave V4 Smart ContractsChainSecurityNot recorded (see the report)Open
Aave V4Trail of BitsNot recorded (see the report)Open

Who can upgrade this contract

Read on Ethereum on 14 Nov 2026, from public data (an RPC node and the upgrade events). Aave: every contract read

Contract
ATokenInstance
Proxy
EIP-1967 (UUPS or admin elsewhere), implementation 0xadc45df3cf1584624c97338bef33363bf5b97ada
Who can upgrade
Contract 0xdabad81af85554e9ae636395611c58f7ec1aaec5, owned by Contract 0x5300a1a15135ea4dc7ad5a167152c01efc9b192a, owned by 0xdabad81af85554e9ae636395611c58f7ec1aaec5 (which owns it in turn) (the account the last upgrade went through)
Upgrades on record
3: first 2025-07-03, last 2026-01-16

The audit that names this code

The Pashov Audit Group report of 1 Oct 2024 names the code of this contract at commit dd0bbecb (read on Ethereum on 14 Nov 2026).

The commit the report names

The Aave security record · Every Aave address · This address on the explorer