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 revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) for Unipilot measures the average daily protocol revenue generated per daily active user. This metric helps assess the monetization efficiency of Unipilot's yield aggregator platform by dividing the protocol's daily revenue by the number of unique users interacting with vaults each day. ARPU is calculated as: Daily Protocol Revenue ÷ Daily Active Users.

## 2. Data sources

The ARPU calculation relies on several types of blockchain data and external feeds:

- **Vault contract events**: Parsed `FeesSnapshot` events from Unipilot vault contracts showing collected fees in underlying tokens, and `Deposit`/`Withdraw` events capturing user interactions
- **Factory contract events**: Parsed `VaultCreated` events from Unipilot factory contracts that define vault addresses and their underlying token pairs
- **Multi-chain coverage**: Event data from Ethereum, BSC, Polygon, and Arbitrum networks covering both active and passive vault types
- **End-of-day price feeds**: Token price data for USD conversion of fee amounts collected in various tokens
- **Token metadata**: Token symbols, decimal places, and contract addresses for proper data processing

## 3. Step-by-step calculation

### Component A: Daily active users

- **Purpose**: Count unique users interacting with Unipilot vaults each day
- **Logic**: Extract user addresses from `Deposit` and `Withdraw` events across all Unipilot vaults on supported chains. Deposit events capture the `depositor` address while withdraw events capture the `recipient` address. Users are classified as either 'Depositor' or 'Withdrawer' based on their interaction type. Daily deduplication is performed using HyperLogLog (HLL) counting to efficiently handle large user datasets and provide approximate distinct counts.
- **Key fields**: `depositor` and `recipient` addresses from vault events, `block_timestamp` for daily grouping, `chain` for multi-chain aggregation

### Component B: Fee collection tracking

- **Purpose**: Capture fees collected by Unipilot vaults from liquidity provision activities
- **Logic**: Parse `FeesSnapshot` events emitted by both active and passive Unipilot vault contracts. These events contain `fees0` and `fees1` amounts representing fees collected in the two underlying tokens of each vault's liquidity pair. Fee amounts are linked to specific tokens using vault dimension data from `VaultCreated` events that define the `tokenA` and `tokenB` addresses for each vault.
- **Key fields**: `fees0` and `fees1` amounts from fee snapshot events, `vault_address` for linking to token pairs, `block_timestamp` for daily aggregation

### Component C: Fee to USD conversion

- **Purpose**: Convert collected fees from various tokens to USD values
- **Logic**: Join fee data with token metadata to get decimal places for each token, then apply decimal corrections to convert from blockchain integer values to human-readable amounts. Convert token amounts to USD using end-of-day price feeds, matching fees to prices by date and token address. Each fee snapshot produces two rows of USD-denominated fee data, one for each token in the vault pair.
- **Key fields**: `amount0` and `amount1` converted to USD, `token_address` for price matching, `timestamp` for daily price alignment

### Component D: Protocol revenue calculation

- **Purpose**: Calculate Unipilot's protocol revenue from collected fees
- **Logic**: Apply protocol fee cuts to the total USD-denominated fees collected. The protocol takes 20% of collected fees before February 20, 2023, and 10% afterward, with Ethereum maintaining the higher rate for a longer period. This represents Unipilot's revenue share from the fees generated by liquidity provision activities in their managed vaults.
- **Key fields**: `fees` multiplied by protocol cut percentage, `timestamp` for applying correct fee rate, `chain_id` for chain-specific fee logic

### Final aggregation

- **Combining components**: Daily revenue amounts are summed across all tokens and chains. Daily active users are aggregated using HyperLogLog merge operations to get total unique users across chains and interaction types. Both metrics use the same daily time boundaries for consistent temporal alignment.
- **Currency conversion**: All fee amounts are converted to USD using end-of-day token prices, ensuring consistent currency denomination across different vault token pairs
- **Time aggregation**: Data is aggregated by calendar day using timestamp truncation, with consistent daily boundaries applied to both revenue and user metrics
- **Final calculation**: ARPU is computed by dividing the daily protocol revenue (sum of all protocol fee cuts in USD) by the daily active user count (distinct users from HLL aggregation). Missing days are filled with zero values to maintain consistent time series data.

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

UnipilotPILOT

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape