website

twitter

github

Stablecoin issuers

Fathom

# Fathom Active users (weekly) Methodology

## 1. Overview

Weekly Active Users (WAU) measures the number of distinct users who interact with Fathom protocol within any 7-day rolling window. This metric captures user engagement across Fathom's two main products: Fathom DEX (automated market maker) and Fathom Lending. The calculation uses HyperLogLog data structures for efficient distinct counting and provides dimensional breakdowns by project, chain, user type, and product.

## 2. Data sources

- **XDC Network DEX events**: Parsed `Pair_Swap_event` logs from Fathom DEX v2 contracts capturing trading activity
- **XDC Network transaction records**: Transaction metadata providing user addresses and execution context  
- **XDC Network lending events**: Multiple parsed event types from Fathom Lending v3 contracts:
  - `LendingPool_Supply_event` logs for deposit activities
  - `LendingPool_Withdraw_event` logs for withdrawal activities  
  - `LendingPool_Borrow_event` logs for borrowing activities
  - `LendingPool_FlashLoan_event` logs for flash loan activities
  - `LendingPool_Repay_event` logs for loan repayment activities

## 3. Step-by-step calculation

### Component A: DEX user identification
- **Purpose**: Identifies daily active traders on Fathom DEX
- **Logic**: Extracts user addresses from XDC Network `Pair_Swap_event` logs, joins with transaction records to get the actual transaction sender address. Classifies all DEX users as "Trader" type and assigns them to the "Fathom DEX" product. Groups by day to create daily user sets.
- **Key fields**: User address (`user_address`), transaction timestamp (`block_timestamp`), chain identifier, and user classification as "Trader"

### Component B: Lending user identification  
- **Purpose**: Identifies daily active users across all Fathom Lending activities
- **Logic**: Combines users from five different lending event types, each with specific user type classifications. Supply events identify "Depositor" users, withdraw events identify "Withdrawer" users, borrow events identify "Borrower" users, flash loan events identify "Borrower" users (using the initiator address), and repay events identify "Repayer" users. All lending users are assigned to the "Fathom Lending" product.
- **Key fields**: User address (`user_address`), event timestamp (`block_timestamp`), user type classification, and product assignment

### Component C: Daily active user aggregation
- **Purpose**: Creates daily distinct user counts with HyperLogLog sketches
- **Logic**: Combines DEX and lending users, truncates timestamps to daily grain, and creates HyperLogLog sketches for efficient distinct counting. Groups by day, chain, user type, and product to prepare for rolling window calculations.
- **Key fields**: Daily timestamp (`timestamp`), HyperLogLog sketch (`hll`), dimensional attributes for grouping

### Component D: Rolling window construction
- **Purpose**: Creates 7-day rolling windows for WAU calculation
- **Logic**: Uses a datespine to generate all calendar days without gaps, then creates a join table that maps each day to the previous 6 days (creating 7-day windows). This ensures every day has a complete 7-day lookback period even when some days have no activity.
- **Key fields**: Target date (`timestamp`) and join dates (`joinday`) for the rolling window

### Component E: Window aggregation
- **Purpose**: Merges daily HyperLogLog sketches across 7-day windows
- **Logic**: Joins the rolling window structure with daily HLL sketches, merging all HLL sketches within each 7-day window to create a single sketch representing distinct users across the full period. Groups by target date and dimensional attributes.
- **Key fields**: Window timestamp, merged HyperLogLog sketches, dimensional groupings

### Final aggregation
- **Combining components**: Creates four separate dimensional views - project-level (all dimensions collapsed), chain-level, user type-level, and product-level - then combines them using union operations
- **Currency conversion**: Not applicable for user count metrics
- **Time aggregation**: Uses 7-day rolling windows with daily boundaries, where each day represents the distinct users active in that day plus the previous 6 days
- **Final calculation**: Extracts the final distinct user count from the merged HyperLogLog sketches using the `hll_count.extract()` function, applies the `finalize_metric_user_wau` macro for standardization and zero-filling of missing days

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

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

Fathom

Active users (weekly)

Active users (weekly)

Competitive landscape