Unipilot removes the complexities and costs of providing concentrated liquidity, making liquidity more capital efficient. For projects, this optimization of liquidity enables lower-slippage trading.

Unipilot is a concentrated liquidity manager live on multiple chains and DEXs. Unipilot currently supports Uniswap V3 and QuickSwap V3 across six chains: Ethereum, Polygon, Polygon zkEVM, Arbitrum, BNB Chain and Dogechain. Unipilot is in the Xord.com ecosystem. This dashboard does not take into account Unipilot's transition into A51 Finance.


PILOT tokenholders own and govern the protocol. PILOT stakers earn a share of the total LP fees (revenue).

github

twitter

etherscan

website

Asset management

Unipilot

# Unipilot Average fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average daily fee revenue generated per active user on the Unipilot protocol. This metric answers the question: "How much fee revenue does Unipilot generate per user on average each day?" The calculation divides total daily fee revenue (in USD) by the number of daily active users, providing insight into user monetization efficiency across Unipilot's yield aggregation platform.

## 2. Data sources

The AFPU calculation uses the following raw data sources:

- **Blockchain events**: Parsed `Deposit` and `Withdraw` events from Unipilot ActiveVault and PassiveVault smart contracts deployed on Ethereum, BSC, Polygon, and Arbitrum networks
- **Fee events**: Parsed `FeesSnapshot` events from the same Unipilot vault contracts that capture accumulated fee amounts in vault token pairs
- **Contract creation events**: Parsed `VaultCreated` events from Unipilot ActiveFactory and PassiveFactory contracts that establish vault-to-token mappings
- **External data**: End-of-day price feeds for token-to-USD conversions and token metadata containing decimal place specifications and symbol information
- **Transaction data**: Blockchain transaction records containing timestamps, hashes, and log indices for event ordering and deduplication

## 3. Step-by-step calculation

### Component A: Daily active user identification

- **Purpose**: Count unique users interacting with Unipilot vaults each day
- **Logic**: Extract user addresses from `Deposit` and `Withdraw` events across Unipilot ActiveVault and PassiveVault contracts on Ethereum, BSC, Polygon, and Arbitrum. Users are classified as either "Depositor" (from `depositor` field in Deposit events) or "Withdrawer" (from `recipient` field in Withdraw events). Events are grouped by day using block timestamps truncated to daily boundaries. Unique users per day are counted using HyperLogLog sketches to efficiently handle deduplication when users perform multiple transactions in a single day
- **Key fields**: Block timestamp for daily grouping, `depositor` and `recipient` addresses as user identifiers, chain information for multi-chain aggregation, transaction hashes for event uniqueness

### Component B: Vault dimension mapping

- **Purpose**: Establish relationships between vault addresses and their underlying token pairs
- **Logic**: Process `VaultCreated` events from Unipilot ActiveFactory and PassiveFactory contracts to create a lookup table mapping vault addresses to their constituent token pairs. Each vault contains two tokens identified by `tokenA` and `tokenB` addresses. Token metadata is joined to provide symbol information creating vault titles in "TOKEN0-TOKEN1" format
- **Key fields**: `vault` address as primary identifier, `tokenA` and `tokenB` addresses for token pair mapping, token symbols for vault naming

### Component C: Fee revenue calculation

- **Purpose**: Calculate total daily fee revenue generated across all Unipilot vaults
- **Logic**: Collect `FeesSnapshot` events from ActiveVault and PassiveVault contracts containing accumulated fee amounts in `fees0` and `fees1` fields representing fees for each token in the vault pair. Split each snapshot into separate records for token0 and token1 fees using the vault dimension mapping to identify specific token addresses. Convert raw token amounts to properly decimalized values based on token metadata, then convert to USD using end-of-day price feeds matched by token address and date. Sum all converted fee amounts by day across all chains and vaults
- **Key fields**: `fees0` and `fees1` amounts from snapshots, vault addresses for token mapping, block timestamps for daily aggregation, token addresses for price lookups

### Final aggregation

- **Combining components**: Daily fee revenue totals and daily active user counts are joined by date to create complete daily records for AFPU calculation
- **Currency conversion**: All fee amounts are converted to USD using end-of-day token price feeds with proper decimal adjustment based on token specifications
- **Time aggregation**: Both user counts and fee revenues use daily boundaries defined by truncating block timestamps to day level
- **Final calculation**: AFPU is computed by dividing total daily fee revenue (sum of all vault fees in USD) by the count of daily active users (unique addresses from deposit/withdraw events). Days with no activity receive zero values through gap-filling logic to maintain time series continuity. Data is filtered to exclude records after December 28, 2023 for both user and fee calculations

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

UnipilotPILOT

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape