DeepGyre/Entities/Aave

Aave

protocolverified
$1.08B
tracked value (priced positions only)
9
addresses claimed
1
chains
2026-11-08 00:00 UTC
complete sweep

Tracked value, last 90 days

Aave: tracked value, last 90 days$3.7M$383.7M$763.8M$1.14B$1.52B2026-09-242026-11-08
400 complete sweeps. A sweep that did not reach every address is left out rather than drawn as an outflow.

Largest holdings

TokenChainAmountValue
USDCethereum311.45M$311.4M
spWETHethereum103K$230.3M
USDTethereum161.03M$160.8M
WEETHethereum62K$153.2M
XAUTethereum32K$129.6M
spwstETHethereum34K$95.2M
USATethereum279K$278K
AUSDCethereum50K$50K
RSETHethereum8.93$22K
ETHethereum4.68$10K

242 further position(s) have no market that can price them (! bimarket.io - World Cu, ?, AFK, AIFreeUse.cc, AIFreeUse.pro, AIG, AILife, AIMevBot.cc…). They are listed as unpriced and left out of the total — never counted as $0.

Value by chain

Value by chainethereum$1.08B

Observed flows, last 7 days

Not observed yet — the flow graph holds no observed links for this entity's 9 address(es) in the last 7 day(s) — the graph is self-building and fills as those addresses are visualised. No rows is not a quiet week.

Addresses

AddressChainLabelClaim
0x4965f6fa20fe9728decf5165016fc338a5a85abfethereumAave: Proxyverified
0x2ecf2a2e74b19aab2a62312167aff4b78e93b6c5ethereumAave: Routerverified
0x4365f8e70cf38c6ca67de41448508f2da8825500ethereumAave: Deployerverified
0xfe1a6056ee03235f30f7a48407a5673bbf25ed48ethereumAave: Deployerverified
0x89c51828427f70d77875c6747759fb17ba10ceb0ethereumAave: Treasuryverified
0x7a1285a7381a3099bfe6706549859316e6f90e6aethereumAave: Deployer 1verified
0x98c23e9d8f34fefb1b7bd6a91b7ff122f4e16f5cethereumAaveexplorer_attributed
0xed0c6079229e2d407672a117c22b62064f4a4312ethereumAaveexplorer_attributed
0x23878914efe38d27c4d67ab83ed1b93a74d4086aethereumAaveexplorer_attributed

Each address is a CLAIM with its level: verified (the entity or a disclosure says so), inferred (traced, corroborated), or community.

How this page is built

DeepGyre tracks Aave by following the on-chain addresses attributed to the protocol — each one a claim with a stated level of evidence, listed in the table above. The tracked value is the sum of what those addresses hold right now: every position with a market price is priced, and positions no market can price are counted and listed separately instead of being valued at zero. An aggregator sweeps the addresses and refreshes the figures; a sweep that did not reach every address is labelled partial, and the page says so rather than presenting a floor as a total.

The value history is drawn from complete sweeps only. A sweep that missed addresses is excluded from the chart, because a lower total from an incomplete look would read as an outflow that never happened. Observed flows work the same way: transfers the flow graph actually saw over the last seven days, between the addresses it has reached — a floor, never the whole story.

Nothing here is a judgment of the protocol's health or solvency. On-chain balances show what the claimed addresses hold; they do not show liabilities, off-chain custody, or addresses nobody has attributed. When an attribution is wrong, the figures inherit the error — which is why every claim keeps its verification level and its source on the page.

Frequently asked

Is this the protocol's full portfolio?

No. It is the sum of the addresses attributed to it on chains DeepGyre scans. Custody held off-chain, unattributed wallets and liabilities are not on the chain and not on this page.

Why did the tracked value change?

Two ways: the chain moved (deposits, withdrawals, price moves on held tokens) and the aggregator swept again. The history chart draws complete sweeps so a data gap never looks like an outflow.

Can I follow this entity's transfers live?

Yes — the dashboard link opens the entity in the live app, where the flow graph, address list and alerts update as new blocks land.

Open Aave in the live dashboard →
Descriptive, not advice. Balances are what the chain shows for the addresses claimed above; an attribution can be wrong. Methodology · How entity value is built · Dashboard