# Active users (monthly) Methodology

## 1. Overview

Active users (monthly) measures the number of unique addresses that perform revenue-generating transactions on Deliswap. This metric reflects the monthly liquidity provider and trader engagement within the Deliswap ecosystem, specifically focusing on interactions with its automated market maker (AMM) hooks and Uniswap V4 integrations. By identifying unique transaction signers associated with fee-collecting swaps, the metric provides a clear view of the active participant base for the Deliswap product.

## 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
- **External data**: Asset metadata for pool identification

## 3. Step-by-step calculation

### Component A: Deliswap pool identification

- **Purpose**: To define the scope of relevant liquidity pools managed by Deliswap.
- **Logic**: `Initialize` events from `PoolManager` contracts are filtered by specific hook addresses to identify pools belonging to the Deliswap product. This includes pools utilizing both the standard Uniswap V4 hook and the Deliswap AMM hook. The resulting pool addresses and associated token pairs are used to filter subsequent swap activity.
- **Key fields**: `pool_address`, `hook_address`, `token_address_0`, `token_address_1`

### Component B: Deliswap trade and user extraction

- **Purpose**: To identify unique users participating in revenue-generating swaps.
- **Logic**: Trade data is extracted from two primary sources: `HookSwap` events from `DeliHookConstantProduct` contracts (for AMM hook trades) and `Swap` events from `PoolManager` contracts (for V4 hook trades). These events are joined with `FeeCollected` events from `FeeProcessor` contracts to ensure that only transactions resulting in protocol fees are included. The `sender` address from these events is identified as the active user. Internal protocol buybacks, where the protocol automatically spends accumulated fees to purchase assets, are excluded to ensure the metric reflects organic user activity.
- **Key fields**: `sender` (user identification), `pool_address`, `transaction_hash`

### Component C: Monthly aggregation

- **Purpose**: To calculate the final count of unique monthly participants.
- **Logic**: Unique user addresses identified in the trade extraction phase are aggregated per 30-day window. The calculation uses a 30-day rolling window based on UTC timestamps. Duplicate addresses within the same 30-day window are removed to arrive at the final active users (monthly) count for the Deliswap product.
- **Key fields**: `block_timestamp`, `user_address`

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

Unique revenue-generating users over a rolling 30-day window.

Active users (monthly)

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

Active users (monthly)

Active users (monthly)

Chain breakdown