Name: Aave Active users (daily) Metrics
Creator: Token Terminal
License: https://tokenterminal.com/terms

Lenders deposit funds into Aave and receive interest payments from borrowers (supply-side fees).

Aave is a non-custodial lending protocol built on Ethereum and other adjacent blockchains. Aave was founded by Stani Kulechov and launched in 2017.

AAVE tokenholders own and govern the protocol. They currently take a cut of the total interest paid by borrowers (revenue). Aave’s investors include ParaFi Capital, Framework Ventures, Three Arrows Capital, etc.

governance

github

twitter

discord

etherscan

website

Lending

Aave

Aave | Data breakdown

# Aave Active users (daily) Methodology

## 1. Overview

The Active users (daily) metric is defined as the number of unique addresses from which revenue-generating transactions are sent to Aave within a fixed 24-hour window. This metric is utilized to evaluate protocol adoption, user engagement, and overall utility across Aave V2, Aave V3, and Aave V4. Unique addresses are identified from on-chain interactions such as supplying assets, withdrawing assets, borrowing, repaying loans, initiating flash loans, and executing liquidations. Daily activity is aggregated to provide a comprehensive view of user growth and network effects.

## 2. Data sources

- **Blockchain events**: `Borrow`, `Deposit`, `FlashLoan`, `Repay`, `Supply`, and `Withdraw` events from `LendingPool` and `AMMLendingPool` contracts, `Borrow`, `Repay`, `Supply`, `Withdraw`, and `LiquidationCall` events from `Spoke` contracts, `Supply` and `Withdraw` events from `SupplyLogic` contracts, `Borrow` and `Repay` events from `BorrowLogic` contracts, `FlashLoan` events from `FlashLoanLogic` contracts, and `LiquidationCall` events from `LiquidationLogic` contracts, covering Ethereum, Arbitrum, Avalanche, Base, and 12 other chains

## 3. Step-by-step calculation

### Component A: Aave V2, Aave V3, and Aave V4 EVM user extraction

- **Purpose**: Extract unique user addresses from EVM-based deployments of Aave V2, Aave V3, and Aave V4
- **Logic**: User addresses are extracted from specific event parameters across multiple smart contracts. For `Borrow`, `Repay`, `Supply` (or `Deposit`), and `Withdraw` events, the `user` parameter is captured. For `FlashLoan` events, the `initiator` parameter is extracted. For `LiquidationCall` events on Aave V4, the `liquidator` parameter is captured. These addresses are classified by user type (e.g., Borrower, Repayer, Depositor, Withdrawer, Liquidator) and mapped to their respective products (Aave V2, Aave V3, or Aave V4) based on the emitting contract's version.
- **Key fields**: `block_timestamp`, `transaction_hash`, `user`, `initiator`, `liquidator`, `chain`, `product_id`

### Component B: Aave V3 Aptos user extraction

- **Purpose**: Extract unique user addresses from the Aptos deployment of Aave V3
- **Logic**: User addresses are parsed from events emitted by Aptos Move contracts. For `Supply` and `Withdraw` events from `SupplyLogic` contracts, the `user` parameter is extracted. For `Borrow` and `Repay` events from `BorrowLogic` contracts, the `user` parameter is captured. For `FlashLoan` events from `FlashLoanLogic` contracts, the `initiator` address is extracted. For `LiquidationCall` events from `LiquidationLogic` contracts, both the `liquidator` and the liquidated `user` addresses are captured. These interactions are mapped to Aave V3.
- **Key fields**: `block_timestamp`, `transaction_hash`, `user`, `initiator`, `liquidator`, `chain`, `product_id`

### Component C: Unified aggregation and deduplication

- **Purpose**: Combine all extracted user addresses and calculate daily distinct active users
- **Logic**: All extracted user records from EVM chains and Aptos are combined into a single dataset. The transaction timestamps are truncated to daily granularity using UTC day boundaries. Duplicate addresses are removed within each daily window per chain, product, and user type to isolate unique active users. The final daily active user count is then generated by counting these distinct addresses.
- **Key fields**: `timestamp`, `chain`, `product_id`, `user_type`, `user_address`

*This methodology was automatically generated by Token Terminal's methodology analyzer.*