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 (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Unipilot measures the number of unique addresses that interact with Unipilot's yield optimization vaults each day. This metric captures users who either deposit funds into vaults or withdraw funds from vaults across Unipilot's active and passive vault products. The calculation aggregates user interactions from multiple blockchain networks where Unipilot operates, providing a comprehensive view of daily protocol engagement.

## 2. Data sources

The calculation relies on parsed blockchain events from Unipilot's smart contracts across four networks:
- **Ethereum events**: Parsed `Deposit` and `Withdraw` events from UnipilotActiveVault and UnipilotPassiveVault contracts
- **BSC events**: Parsed `Deposit` and `Withdraw` events from UnipilotActiveVault and UnipilotPassiveVault contracts  
- **Polygon events**: Parsed `Deposit` and `Withdraw` events from UnipilotActiveVault and UnipilotPassiveVault contracts
- **Arbitrum events**: Parsed `Deposit` and `Withdraw` events from UnipilotActiveVault and UnipilotPassiveVault contracts
- **Blockchain metadata**: Block timestamps from transaction records for daily boundary determination

## 3. Step-by-step calculation

### Component A: User event normalization
- **Purpose**: Extract and normalize all user interaction events from Unipilot vault contracts across multiple chains
- **Logic**: The system processes `Deposit` and `Withdraw` events from both active and passive vault contracts on each supported blockchain. For `Deposit` events, the `depositor` parameter identifies the user address and the user type is classified as 'Depositor'. For `Withdraw` events, the `recipient` parameter identifies the user address and the user type is classified as 'Withdrawer'. Each record includes the block timestamp, transaction hash, chain identifier, and standardized business classification metadata including 'asset_management' as the market sector and 'yield_aggregator' as the business segment
- **Key fields**: `block_timestamp` for temporal aggregation, `user_address` extracted from event parameters, `user_type` classification, `chain` identifier, and business metadata fields

### Component B: Daily user aggregation
- **Purpose**: Count unique users per day by truncating timestamps to daily boundaries and removing duplicates
- **Logic**: The system truncates block timestamps to day boundaries using timestamp truncation, creating a daily time grain. Within each day, chain, and user type combination, the calculation identifies distinct user addresses to avoid double-counting users who make multiple transactions in the same day. The aggregation preserves chain-level granularity to enable cross-chain analysis while maintaining user type distinctions between depositors and withdrawers
- **Key fields**: `timestamp` truncated to daily boundaries, `user_dau` representing unique user addresses, granularity dimensions including `chain` and `user_type`

### Final aggregation
- **Combining components**: The normalized user events are directly aggregated without additional joining, as all necessary data is already contained within the event stream
- **Time boundaries**: Daily boundaries are determined by truncating block timestamps to day precision, ensuring consistent time zone handling across all chains
- **Data filtering**: The calculation excludes all data from December 28, 2023 onwards, likely due to data quality or business logic requirements. Additionally, chain availability filtering is applied to ensure only data from operational chains is included
- **Final calculation**: The result provides daily unique user counts segmented by chain and user type, enabling analysis of both overall daily active users and breakdown by interaction type (deposits vs withdrawals) and blockchain network

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

Unique revenue-generating users over a fixed 24-hour window.

UnipilotPILOT

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown