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 Active users (monthly) Methodology

## 1. Overview

Monthly Active Users (MAU) measures the number of unique users who interact with Unipilot protocol within any 30-day rolling window. This metric tracks user engagement across Unipilot's yield aggregation services on multiple blockchains by counting distinct users who deposit or withdraw from Active and Passive vault contracts. The calculation uses HyperLogLog probabilistic data structures to efficiently compute unique user counts across overlapping time periods and provides breakdowns by blockchain, user type, and product dimensions.

## 2. Data sources

The metric relies on the following raw data sources:

- **Blockchain event logs**: Parsed smart contract events from Unipilot V2 protocol across Ethereum, BSC, Polygon, and Arbitrum blockchains
- **Deposit events**: `Deposit` events from both UnipilotActiveVault and UnipilotPassiveVault contracts containing `depositor` addresses
- **Withdrawal events**: `Withdraw` events from both UnipilotActiveVault and UnipilotPassiveVault contracts containing `recipient` addresses  
- **Transaction metadata**: Block timestamps and transaction hashes from blockchain transaction records
- **Chain availability data**: Blockchain network availability and operational status information

## 3. Step-by-step calculation

### Component A: User interaction extraction
- **Purpose**: Identifies and normalizes all user interactions with Unipilot vaults across supported blockchains
- **Logic**: Extracts user addresses from Unipilot V2 smart contract events on Ethereum, BSC, Polygon, and Arbitrum. For `Deposit` events, captures the `depositor` parameter as the user address and classifies as 'Depositor' user type. For `Withdraw` events, captures the `recipient` parameter as the user address and classifies as 'Withdrawer' user type. Associates each interaction with blockchain metadata including `block_timestamp`, `transaction_hash`, and `chain` identifier. Applies standard business categorization with `market_sector_id` as 'asset_management' and `business_segment_id` as 'yield_aggregator'
- **Key fields**: `user_address` (depositor or recipient), `user_type` (Depositor/Withdrawer), `block_timestamp`, `chain`, `transaction_hash`

### Component B: Daily active user aggregation  
- **Purpose**: Creates daily snapshots of unique active users across all dimensions
- **Logic**: Groups user interactions by daily time boundaries using `timestamp_trunc` on `block_timestamp`. Generates distinct user counts per day, grouped by `chain`, `user_type`, `market_sector_id`, `business_segment_id`, and `product_id`. Applies temporal filter to exclude data after 2023-12-28. Creates base daily active user dataset with grain set to 'day'. Applies chain availability filtering to ensure data quality across supported blockchains
- **Key fields**: `timestamp` (daily), `timestamp_grain`, `chain`, `user_type`, `product_id`, `user_dau` (user address)

### Component C: Rolling window construction
- **Purpose**: Creates 30-day sliding windows for MAU calculation using continuous time series
- **Logic**: Generates comprehensive datespine covering all days from minimum historical date to current date minus one day using `generate_timestamp_array`. For each date in the datespine, creates 30-day lookback window by generating array of dates from 29 days prior through the current date. Joins datespine windows with daily user data to create complete time series without gaps. Converts daily user sets to HyperLogLog sketches with 15-bit precision for efficient distinct counting across overlapping periods
- **Key fields**: `timestamp` (window end date), `joinday` (dates within 30-day window), `hll` (HyperLogLog sketch of users)

### Component D: Dimensional MAU calculation
- **Purpose**: Computes MAU across different analytical dimensions while maintaining user uniqueness
- **Logic**: Creates four separate dimensional breakdowns of MAU data. For project-level MAU, merges all HyperLogLog sketches across all dimensions to get total unique users. For chain-level breakdown, groups by `chain_id` and merges HLL sketches within each chain. For user-type breakdown, groups by `user_type` and merges sketches for Depositors and Withdrawers separately. For product-level breakdown, groups by `product_id` and merges sketches within each product. Uses `hll_count.merge_partial` to combine sketches and `hll_count.extract` to get final distinct user counts
- **Key fields**: `dimensions` (breakdown type), `chain_id`, `user_type`, `product_id`, `user_mau` (distinct user count)

### Final aggregation
- **Combining components**: Unions all dimensional breakdowns (project, chain, user type, product) into single result set using `union all` operations. Each breakdown maintains its specific dimensional values while setting non-relevant dimensions to null
- **Time aggregation**: Uses daily grain with 30-day rolling windows. Each day represents the count of unique users active in the trailing 30-day period ending on that date
- **Final calculation**: Applies `finalize_metric_user_mau` macro with 'fill_zeros' strategy to standardize schema, add metadata fields, and fill missing dates with zero values. Sets `data_id` to 'unipilot' for identification
- **Incremental processing**: For incremental updates, processes data from 29 days plus incremental lookback period before the last modified timestamp to ensure complete window coverage

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

Unique revenue-generating users over a rolling 30-day window.

UnipilotPILOT

Active users (monthly)

Active users (monthly)

Competitive landscape

Chain breakdown