Infrastructure

bloXroute

# bloXroute Average revenue per user (ARPU) Methodology

## 1. Overview

BloxRoute ARPU (Average Revenue Per User) measures the average daily revenue generated per active user of BloxRoute's services. This metric is calculated by dividing total daily revenue by the number of daily active users. The metric helps assess BloxRoute's monetization efficiency and user value. The calculation uses Solana blockchain data where users pay fees to BloxRoute's services, with all amounts converted to USD for standardized reporting.

## 2. Data sources

- **Solana native transfers**: Raw Solana blockchain transfer events from the native SOL token, specifically transfers directed to BloxRoute's fee collection addresses
- **End-of-day price feeds**: Token price data used to convert SOL amounts to USD values  
- **Token metadata**: Solana token information including decimal precision for proper amount calculations

## 3. Step-by-step calculation

### Component A: Fee extraction
- **Purpose**: Identify and extract fee payments made to BloxRoute services
- **Logic**: Filter Solana native transfers to capture payments sent to BloxRoute's fee collection address `HWEoBxYs7ssKuudEjzjmpfJVX7Dvi7wescFsVx2L5yoY`. Exclude self-transfers where the fee collection address is also the transaction sender, ensuring only genuine user payments are captured. Each transfer record includes the transaction signer as the user identifier and the transfer amount in lamports.
- **Key fields**: `block_timestamp` for timing, `transaction_signer` for user identification, `amount` in lamports, and `to_address` for fee collection validation

### Component B: Revenue calculation  
- **Purpose**: Convert raw fee amounts to standardized USD revenue values
- **Logic**: Take the filtered fee transfers and convert amounts from lamports to SOL by dividing by 1e9. Apply daily timestamp truncation and group by day, chain, product, and token address. Sum the SOL amounts for each day and convert to USD using end-of-day price feeds. The conversion process handles decimal precision and applies appropriate exchange rates.
- **Key fields**: Daily aggregated `fees` converted to USD, `timestamp` truncated to day granularity, `chain_id` as 'solana', and `token_address` for SOL

### Component C: User counting
- **Purpose**: Count distinct daily active users efficiently across different dimensional breakdowns
- **Logic**: Extract unique transaction signers from the fee payment data on a daily basis. Use HyperLogLog (HLL) aggregation to efficiently count distinct users, which allows for scalable computation across large datasets. Create multiple dimensional breakdowns including project-level totals, chain-level counts, user type breakdowns, and product-level segmentation. Each breakdown uses HLL merge operations to maintain accuracy while enabling efficient aggregation.
- **Key fields**: `user_dau` containing distinct user counts, `timestamp` for daily boundaries, dimensional fields like `chain_id`, `product_id`, and `user_type` for breakdowns

### Final aggregation
- **Combining components**: The revenue values from Component B are joined with user counts from Component C using the ARPU calculation macro, which performs the division of total daily revenue by daily active user count
- **Currency conversion**: All amounts are converted to USD using end-of-day price feeds, with SOL amounts first converted from lamports (÷1e9) then multiplied by USD exchange rates
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, ensuring consistent daily snapshots
- **Final calculation**: ARPU equals total daily revenue in USD divided by the count of distinct daily active users, with missing days filled with zero values to maintain continuous time series data

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

bloXroute

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape