# Deliswap Trade count Methodology

## 1. Overview

Trade count measures the number of trades executed on a decentralized exchange. It shows how frequently users are buying or selling assets through the project. For Deliswap, this metric captures all successful swap transactions processed through the protocol's constant product AMM hooks and Uniswap V4 hook integrations.

## 2. Data sources

- **Blockchain events**: `HookSwap` events from `DeliHookConstantProduct` contracts, `Swap` and `Initialize` events from `PoolManager` contracts, and `FeeCollected` events from `FeeProcessor` contracts, covering Base.

## 3. Step-by-step calculation

### Component A: Deliswap pool identification

- **Purpose**: Identify the specific liquidity pools belonging to the Deliswap product.
- **Logic**: `Initialize` events from `PoolManager` contracts are parsed to identify pools associated with Deliswap-specific hook addresses. The pool identifiers, token addresses, and fee tiers are extracted to create a reference directory of valid Deliswap pairs.
- **Key fields**: `id` (pool identifier), `hooks` (hook address), `currency0` (token address), `currency1` (token address).

### Component B: AMM hook trade extraction

- **Purpose**: Capture trade activity occurring through the native constant product AMM hook.
- **Logic**: `HookSwap` events from `DeliHookConstantProduct` contracts are extracted. These events are joined with `FeeCollected` events from `FeeProcessor` contracts using the transaction hash and pool identifier. This join ensures that only valid, fee-generating user trades are included while internal protocol buybacks—where accumulated fees are used to purchase assets—are excluded.
- **Key fields**: `transaction_hash`, `id` (pool identifier), `sender`.

### Component C: Uniswap V4 hook trade extraction

- **Purpose**: Capture trade activity occurring through the Uniswap V4 hook infrastructure.
- **Logic**: `Swap` events from `PoolManager` contracts are parsed. Similar to the AMM hook extraction, these events are joined with `FeeCollected` events from `FeeProcessor` contracts. This process filters the broader Uniswap V4 activity to isolate transactions specifically interacting with Deliswap hooks.
- **Key fields**: `transaction_hash`, `id` (pool identifier), `sender`.

### Component D: Trade count aggregation

- **Purpose**: Consolidate trade data and calculate the final frequency metric.
- **Logic**: Identified trades from both the AMM and Uniswap V4 hooks are unified into a single dataset. The metric is calculated by counting the number of unique transaction hashes per day. Data is aggregated at a daily granularity using UTC day boundaries, and any days without activity are zero-filled to ensure a continuous time series.
- **Key fields**: `transaction_hash`, `block_timestamp`.

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

Number of trades executed on a decentralized exchange.

Trade count

Exchanges (DEX)

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

BMX is a non-custodial exchange for spot and perpetual contracts built on Base. BMX has three product lines: Classic, Freestyle, and Based MediaX

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

Deliswap

Archived

Trade count

Trade count

Chain breakdown