Liquidity providers deposit funds into DFX and receive a share of trading fees (supply-side fees).

DFX is a decentralized foreign exchange protocol deployed on Polygon, Ethereum & Arbitrum. DFX was founded in 2021 by Kevin Zhang and Adrian Li.

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

governance

github

twitter

discord

etherscan

website

Exchanges (DEX)

DFX Finance

# DFX Finance Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for DFX Protocol measures the count of unique wallet addresses that executed trades on any DFX AMM pool within a single day. This metric tracks user engagement by identifying distinct traders across all supported chains and protocol versions, providing insight into the daily trading activity and user base size of the DFX decentralized exchange platform.

## 2. Data sources

The calculation uses the following raw data sources:
- **DFX smart contract events**: Parsed `Trade` events from DFX v1 Curve AMM contracts on Ethereum and Polygon
- **DFX smart contract events**: Parsed `CurveV2_Trade` events from DFX v2 AMM contracts on Ethereum and Polygon  
- **DFX smart contract events**: Parsed `CurveV22_Trade` events from DFX v2 AMM contracts on Ethereum, Polygon, and Arbitrum
- **Transaction data**: Ethereum, Polygon, and Arbitrum transaction records containing sender address information
- **Chain metadata**: Chain availability filters to ensure data quality across supported networks

## 3. Step-by-step calculation

### Component A: Trade event collection
- **Purpose**: Gather all trading activity from DFX AMM pools across all protocol versions and chains
- **Logic**: Collect parsed smart contract events from multiple DFX contract types including `Curve_Trade_event` for v1 pools, `CurveV2_Trade_event` for v2 pools, and `CurveV22_Trade_event` for v2.2 pools. Events are sourced from Ethereum, Polygon, and Arbitrum networks depending on protocol version availability. Each event contains trade details including token addresses, amounts, and transaction metadata.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for linking to transaction data, `address` for contract identification, `originAmount` and `targetAmount` for trade volumes, `origin` and `target` for token addresses

### Component B: User address resolution
- **Purpose**: Identify the actual wallet address that initiated each trade transaction
- **Logic**: Join trade events with transaction records using the `transaction_hash` to obtain the `from_address` field from the transaction. This resolves the actual user wallet that signed and submitted the trading transaction, as opposed to any intermediate contract addresses that may appear in the trade event itself.
- **Key fields**: `from_address` becomes `user_address` representing the trading wallet, `transaction_hash` for joining trade events to transactions

### Component C: Daily user aggregation  
- **Purpose**: Count unique active users per day across all chains and protocol versions
- **Logic**: Truncate `block_timestamp` to daily boundaries using day-level granularity. Group all trades by the resulting date and count distinct `user_address` values to identify unique traders per day. This creates one record per unique user per day regardless of how many trades they performed.
- **Key fields**: `timestamp` truncated to daily level, `user_address` for unique user identification, `chain` for network attribution

### Final aggregation
- **Combining components**: Trade data from all DFX protocol versions and chains is combined into a unified dataset before aggregation
- **Currency conversion**: Not applicable for user counting metrics  
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day-level granularity
- **Final calculation**: The metric value is the count of distinct wallet addresses that executed at least one trade on DFX AMM pools within each calendar day, with all users classified as 'Trader' type and attributed to the 'exchanges' market sector and 'dex' business segment

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

Unique revenue-generating users over a fixed 24-hour window.

DFX FinanceDFX

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown