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 Supply-side fees Methodology

## 1. Overview

Supply-side fees represent the portion of trading fees that Unipilot distributes to liquidity providers after deducting the protocol's fee share. This metric answers the question: "How much value does Unipilot distribute to its liquidity providers?" The calculation takes total fees collected from trading activity across all Unipilot vaults and subtracts the protocol fee cut, which varies by chain and time period.

## 2. Data sources

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

- **Vault creation events**: Parsed `VaultCreated` events from Unipilot Active Factory and Passive Factory contracts across Ethereum, Polygon, Arbitrum, and BSC networks
- **Fee snapshot events**: Parsed `FeesSnapshot` events from Unipilot Active Vault and Passive Vault contracts that record accumulated trading fees
- **Token metadata**: Token symbol information and decimal precision data for fee token identification and standardization
- **End-of-day price feeds**: Daily token price data for USD conversion of fee amounts

## 3. Step-by-step calculation

### Component A: Vault identification and metadata
- **Purpose**: Establish the universe of Unipilot vaults and their underlying token pairs
- **Logic**: Collect all `VaultCreated` events from both Active Factory and Passive Factory contracts across supported chains. Extract vault address, token0 address, token1 address, and create descriptive vault titles by concatenating token symbols. Join with token metadata to enrich vault information with human-readable token symbols.
- **Key fields**: `vault_address`, `token0_address`, `token1_address`, `vault_title`, `chain`, `version`

### Component B: Fee snapshot collection
- **Purpose**: Capture fee accumulation data from individual vault contracts
- **Logic**: Gather all `FeesSnapshot` events emitted by Unipilot vault contracts when fees are collected or withdrawn. These events record the accumulated fees in both tokens of each vault's pair. Extract block timestamp, vault address, and fee amounts for both tokens.
- **Key fields**: `block_timestamp`, `vault_address`, `amount0` (fees in token0), `amount1` (fees in token1), `chain`

### Component C: Fee data preparation and conversion
- **Purpose**: Transform fee snapshot data into a standardized daily format with USD values
- **Logic**: Join fee snapshots with vault metadata to identify which tokens the fees represent. Split each snapshot into two separate records - one for token0 fees and one for token1 fees. Truncate timestamps to daily boundaries for consistent aggregation. Convert raw token amounts to USD values using end-of-day price feeds and apply decimal corrections based on each token's precision.
- **Key fields**: `timestamp` (daily), `chain_id`, `token_address`, `fees` (in USD)

### Component D: Total fees aggregation
- **Purpose**: Sum all fees across vaults and time periods to get total protocol fees
- **Logic**: Aggregate the converted USD fee amounts by day and chain, summing across all vaults and both tokens in each pair. Apply metric finalization processes including schema validation and gap filling with zeros for missing days.
- **Key fields**: `timestamp`, `chain_id`, `fees` (total daily fees in USD)

### Component E: Supply-side fee calculation
- **Purpose**: Calculate the portion of fees distributed to liquidity providers after protocol fee deduction
- **Logic**: Apply time and chain-dependent protocol fee rates to determine supply-side fees. For Ethereum transactions before February 20, 2023, subtract a 20% protocol fee from total fees. For all other cases (other chains or Ethereum after the fee change), subtract a 10% protocol fee. The remaining amount represents fees distributed to liquidity providers.
- **Key fields**: `fees_supply_side` (total fees minus protocol cut)

### Final aggregation
- **Combining components**: The calculation flows linearly from raw events to final metrics, with each component building on the previous one
- **Currency conversion**: USD conversion occurs early in the process using end-of-day token prices with proper decimal adjustment for each token
- **Time aggregation**: All data is aggregated to daily boundaries using timestamp truncation to day
- **Final calculation**: Supply-side fees equal total fees multiplied by (1 minus protocol fee rate), where the protocol fee rate is 0.2 for early Ethereum transactions and 0.1 otherwise

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

Portion of fees distributed to service providers or supply-side participants.

UnipilotPILOT

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown