website

github

twitter

Blockchains (L1)

XDC Network

# XDC Network Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) for XDC measures the average daily revenue generated per active user on the XDC blockchain. This metric answers the business question: "How much revenue does each active user generate on average per day?" The calculation follows the standard ARPU formula by dividing total daily revenue by the number of daily active users. Revenue is derived from transaction fees paid by users, while active users are identified as unique transaction senders.

## 2. Data sources

The ARPU calculation relies on the following raw data sources:

- **XDC blockchain transaction records**: Complete transaction data from the XDC blockchain including sender addresses, gas usage, gas prices, and timestamps
- **End-of-day token price feeds**: XDC token price data for USD conversion
- **XDC token metadata**: Token contract address and symbol information for proper identification

## 3. Step-by-step calculation

### Component A: Revenue calculation from transaction fees

- **Purpose**: Calculates total daily revenue from transaction fees paid on the XDC blockchain
- **Logic**: Processes all XDC transactions to extract gas fees. For each transaction, multiplies `gas_used` by `gas_price` to get the total gas cost in wei, then divides by 1e18 to convert to XDC token units. These XDC amounts are converted to USD using end-of-day price feeds. All transaction fees are summed per day to get total daily revenue.
- **Key fields**: `gas_used` (gas consumed by transaction), `gas_price` (price per gas unit), `block_timestamp` (transaction timestamp), `l1_gas_fee` (calculated fee amount)

### Component B: Daily active user counting

- **Purpose**: Counts unique active users per day on the XDC blockchain
- **Logic**: Identifies unique daily active users from XDC transaction records. Active users are defined as unique transaction senders (`from_address`) per day. Uses HyperLogLog sketching for efficient distinct counting and aggregation. Transactions are grouped by day using timestamp truncation, and distinct sender addresses are counted within each day.
- **Key fields**: `from_address` (transaction sender address), `block_timestamp` (transaction timestamp), `user_address` (processed user identifier), `user_dau` (daily active user count)

### Component C: Multi-dimensional aggregation

- **Purpose**: Provides ARPU breakdowns across different dimensions for comprehensive analytics
- **Logic**: Aggregates user counts across multiple dimensions including project level, chain level, user type, and product level. Uses HyperLogLog merge operations to combine daily sketches while maintaining distinct count accuracy. This enables ARPU calculation at various granularities.
- **Key fields**: `dimensions` (aggregation level), `chain_id` (blockchain identifier), `product_id` (product identifier), `user_type` (user classification)

### Final aggregation

- **Combining components**: Revenue and user metrics are combined using the calculate_arpu macro, which performs the division of total daily revenue by daily active users
- **Currency conversion**: All revenue amounts are converted to USD using end-of-day XDC token price feeds before the final calculation
- **Time aggregation**: Both revenue and user data are aggregated to daily boundaries using timestamp truncation to day level
- **Final calculation**: ARPU = Total Daily Revenue (USD) ÷ Daily Active Users, with zero-filling applied for days with missing data to ensure complete time series coverage

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

XDC NetworkXDC

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape