Liquidity providers deposit funds into QuickSwap and receive trading fees from traders (supply-side fees).

QuickSwap is a non-custodial exchange protocol built on Polygon. QuickSwap was founded by Nick Mudge & Sameep Singhania and launched in 2020.

QUICK tokenholders own and govern the protocol. They currently take a cut of the total trading fees paid by traders (revenue).

github

twitter

discord

etherscan

website

Exchanges (DEX)

QuickSwap

# QuickSwap Trade count Methodology

## 1. Overview

Trade count measures the number of trades executed on QuickSwap. It represents the frequency with which users buy or sell assets through the protocol's automated market maker (AMM) infrastructure. This metric provides insight into the level of activity and liquidity utilization across QuickSwap V2 and QuickSwap V3.

## 2. Data sources

- **Blockchain events**: `Swap` events from `Pair` and `Pool` contracts, covering Polygon, Base, and Manta
- **External data**: Asset metadata for trading pair identification

## 3. Step-by-step calculation

### Component A: Trade event extraction

- **Purpose**: Identify and capture swap transactions across different protocol versions
- **Logic**: `Swap` events are parsed from `Pair` contracts for QuickSwap V2 and `Pool` contracts for QuickSwap V3. Transaction hashes, log indices, and contract addresses are extracted to uniquely identify each trade. These events are joined with native transaction data to associate the trade with the initiating user address.
- **Key fields**: `transaction_hash`, `log_index`, `address`

### Component B: Filtering and metadata enrichment

- **Purpose**: Ensure data quality and exclude invalid trading activity
- **Logic**: Trade events are joined with trading pair metadata to identify the underlying assets. A denylist is applied to exclude specific trading pairs on Polygon that are identified as having limited price feed support or insufficient liquidity. This ensures the metric reflects activity from verified and supported trading pairs.
- **Key fields**: `account_address`, `chain`

### Component C: Trade count aggregation

- **Purpose**: Calculate the final daily trade count per product and chain
- **Logic**: The number of unique transaction hashes is counted and aggregated by day, chain, and product. This approach ensures that the metric reflects the number of successful swap transactions. The final values are zero-filled for any days where no trading activity is recorded to maintain a continuous time series.
- **Key fields**: `transaction_hash`, `product_id`, `chain_id`

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

Number of trades executed on a decentralized exchange.

QuickSwapQUICK

Trade count

Trade count

Competitive landscape

Chain breakdown