Liquidity providers deposit funds into liquidity pools with different liquidity management strategies and receive trading fees from traders (supply-side fees).

Maverick is a non-custodial exchange protocol built on  Ethereum, Binance Smart Chain, Base, and zkSync Era. Maverick was founded by Alvin Xu and Bob Baxley in March 2023.

MAV tokenholders own and govern the protocol. Currently, the protocol does not take a cut of the trading fees. Maverick's investors include Pantera Capital, Binance Labs, Coinbase Ventures, and Apollo Crypto.

github

twitter

discord

etherscan

website

Exchanges (DEX)

Maverick Protocol

# Maverick Protocol Tradeable pairs Methodology

## 1. Overview

The tradeable pairs metric measures the cumulative number of unique trading pairs available on Maverick DEX across supported blockchains. This metric tracks the growth of tradeable assets on the platform by counting distinct token pairs that have liquidity pools created through the Maverick Factory contract. The calculation aggregates new pair creations daily and maintains a running total to show the expanding universe of tradeable assets over time.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Pool creation events**: Parsed `PoolCreated` events from Maverick Factory contracts on Ethereum, BSC, Base, and zkSync Era blockchains containing pool addresses, token pair information, fee structures, and creation timestamps
- **Token metadata**: Token registry data providing token symbols, decimal precision, and contract addresses for pair identification and naming
- **Blockchain transaction data**: Block timestamps from the respective blockchains to determine when pools were created

## 3. Step-by-step calculation

### Component A: Pool creation data extraction
- **Purpose**: Identifies all trading pairs created on Maverick DEX across supported chains
- **Logic**: Extracts `PoolCreated` events from Maverick Factory contracts on Ethereum, BSC, Base, and zkSync Era. Each event contains the `poolAddress` (unique pool identifier), `tokenA` and `tokenB` addresses (the two tokens in the pair), `fee` (trading fee tier), `protocolFeeRatio` (protocol fee percentage), and `block_timestamp` (when the pool was created). Fee values are converted from wei format (18 decimals) to decimal representation by dividing by 10^18.
- **Key fields**: `poolAddress` as unique pool identifier, `tokenA` and `tokenB` as token pair addresses, `fee` and `protocolFeeRatio` as fee structure data, `block_timestamp` for creation timing, `chain` to identify the blockchain

### Component B: Token metadata enrichment
- **Purpose**: Enriches pool data with human-readable token information
- **Logic**: Joins pool creation data with token registry using token addresses and chain identifiers. Retrieves token symbols and decimal precision for both tokens in each pair. Creates standardized pair names in the format "TOKEN0-TOKEN1" using token symbols. Handles cases where token metadata may be missing by using coalesce functions.
- **Key fields**: `symbol` for token names, `decimals` for token precision, `account_name` as the formatted pair name combining both token symbols

### Component C: First appearance identification
- **Purpose**: Determines when each unique trading pair first became available
- **Logic**: Groups pool creation data by chain and `account_address` (pool address). Calculates the minimum `block_timestamp` for each unique pool to identify when it was first created. Truncates timestamps to daily granularity using day-level truncation to aggregate creation events by date. This ensures each trading pair is counted only once on its creation date.
- **Key fields**: `timestamp` (truncated to day), `timestamp_grain` set to 'day', `chain` for blockchain identification, `account_address` for unique pool identification

### Component D: Daily aggregation
- **Purpose**: Counts new trading pairs created each day
- **Logic**: Aggregates first appearance data by date and chain. Counts distinct `account_address` values (pool addresses) for each day and chain combination to determine how many new tradeable pairs were created. This provides the daily increment of new pairs rather than cumulative totals.
- **Key fields**: `timestamp` for date grouping, `chain` for blockchain segmentation, `pair_count` as the count of new pairs created that day

### Component E: Time series gap filling
- **Purpose**: Ensures continuous daily time series with no missing dates
- **Logic**: Applies gap-filling logic to create continuous daily time series for each chain. For dates where no new pairs were created, fills the `pair_count` with zero values. This ensures the time series has entries for every day within the date range, maintaining data continuity for cumulative calculations.
- **Key fields**: `pair_count` filled with zeros for dates without new pair creations

### Final aggregation
- **Combining components**: The daily new pair counts are processed through a cumulative sum calculation partitioned by chain and ordered by timestamp
- **Currency conversion**: Not applicable as this metric counts pairs rather than monetary values
- **Time aggregation**: Daily granularity is maintained throughout the calculation with timestamps truncated to day level
- **Final calculation**: The final tradeable pairs metric is calculated as a running cumulative sum of daily new pair counts, partitioned by chain and ordered chronologically. This produces the total number of unique tradeable pairs available on each chain as of each date. The result is then processed through a finalization macro that standardizes the schema, validates identifiers, and applies forward-filling for any remaining gaps. A chain availability filter is applied to include only supported blockchain data in the final output.

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

Number of unique token pairs available for trading on the exchange.

Maverick ProtocolMAV

Tradeable pairs

Tradeable pairs

Competitive landscape

Chain breakdown