website

twitter

github

Stablecoin issuers

Fathom

# Fathom Average trading volume (per trade) Methodology

## 1. Overview

This metric calculates the average trading volume per trade on Fathom DEX by dividing total daily trading volume (in USD) by the total number of trades executed on the same day. It measures the average size of trades on the Fathom decentralized exchange, helping assess trading behavior and liquidity utilization patterns. The calculation uses a simple division approach where both the numerator (trading volume) and denominator (trade count) are aggregated to daily totals before division.

## 2. Data sources

The calculation relies on several key data sources:

- **Blockchain events**: Parsed `Factory_PairCreated` events and `Pair_Swap` events from Fathom DEX smart contracts on the XDC blockchain
- **Transaction data**: XDC transaction records providing user address information and transaction context
- **Token metadata**: Token symbol and decimal information for proper amount conversion and trading pair identification
- **External data**: End-of-day token price feeds for USD conversion of token amounts

## 3. Step-by-step calculation

### Component A: Trading pairs identification
- **Purpose**: Establishes all valid Fathom DEX trading pairs with their fee structure
- **Logic**: Extracts trading pair information from `Factory_PairCreated` events on XDC blockchain. Each pair consists of two token addresses (`token0` and `token1`) with a fixed fee tier of 0.3% (represented as 3000/1000000). Token metadata is joined to get decimal places and symbols for each token, enabling proper amount conversion and pair naming in the format "TOKEN0-TOKEN1"
- **Key fields**: `account_address` (trading pair contract), `token0_address`, `token1_address`, `token0_decimals`, `token1_decimals`, `fee_tier`

### Component B: Trade event processing
- **Purpose**: Captures and processes all trade execution events from Fathom DEX
- **Logic**: Extracts trade data from `Pair_Swap` events, calculating net token amount changes for each trade. For each swap, the net amount is calculated as (`amount0In` - `amount0Out`) for token0 and (`amount1In` - `amount1Out`) for token1. These represent the actual token amounts exchanged in each direction. Transaction records are joined to capture user addresses and provide transaction context
- **Key fields**: `transaction_hash`, `log_index`, `token0_amount`, `token1_amount`, `user_address`, `account_address`

### Component C: Volume calculation and USD conversion
- **Purpose**: Converts raw token amounts to standardized USD trading volumes
- **Logic**: Joins trade events with trading pairs to obtain token decimal information, then converts raw token amounts to proper decimal format by dividing by 10^decimals. Applies end-of-day USD price feeds to convert token amounts to USD values. The system prioritizes `token0` price for volume calculation, but falls back to `token1` price if `token0` price is unavailable. If neither price is available, the trade volume is recorded as zero. All trades are aggregated to daily totals
- **Key fields**: `trading_volume` (USD), `timestamp`, `token0_amount`, `token1_amount`

### Component D: Trade count aggregation
- **Purpose**: Counts the total number of distinct trades executed daily
- **Logic**: Uses the same underlying trade data from Component B but focuses on counting distinct transaction hashes rather than calculating volumes. This ensures consistency between volume and count calculations since both use identical trade filtering and identification logic. Trades are aggregated to daily totals by counting unique transaction hashes
- **Key fields**: `trade_count`, `timestamp`, `transaction_hash`

### Final aggregation
- **Combining components**: Trading volume and trade count are separately aggregated by timestamp (daily granularity), then joined on timestamp to ensure matching time periods
- **Currency conversion**: All token amounts are converted to USD using end-of-day price feeds, with fallback logic from `token0` to `token1` prices
- **Time aggregation**: Both components use daily timestamp truncation to align all trades within 24-hour periods
- **Final calculation**: The metric is calculated as `safe_divide(trading_volume, trade_count)`, where safe division handles edge cases where trade count might be zero, returning null instead of causing division errors. Missing values are filled with zeros through standardized metric finalization

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

Fathom

Average trading volume (per trade)

Average trading volume (per trade)

Competitive landscape