Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Energy Web X is energy blockchain ecosystem powered by Polkadot Relay chain.

website

twitter

github

etherscan

Blockchains (L2)

Energy Web X

# Energy Web X Average revenue per user (ARPU) Methodology

## 1. Overview

ARPU (Average Revenue Per User) measures the average daily revenue generated per active user on the Energy Web blockchain. This metric helps evaluate user monetization efficiency by dividing total daily protocol revenue by the number of daily active users. The calculation uses transaction fees as the revenue source and unique transaction senders as the user base, providing insight into how effectively the Energy Web protocol generates revenue from its user activity.

## 2. Data sources

- **Energy Web blockchain events**: Parsed events from the Energy Web blockchain, specifically `TransactionFeePaid` events from the `transactionPayment` pallet containing transaction fee and tip information
- **Energy Web transaction records**: Extrinsic records from the Energy Web blockchain containing transaction sender addresses and execution details
- **External price data**: End-of-day price feeds from CoinGecko for the energy-web-token, used for USD conversion of native token amounts
- **Token metadata**: Energy Web token configuration data including decimal precision specifications

## 3. Step-by-step calculation

### Component A: Transaction fee extraction
- **Purpose**: Extract and process transaction fees from Energy Web blockchain events
- **Logic**: Filter Energy Web blockchain events to identify `TransactionFeePaid` events from the `transactionPayment` pallet. Parse the JSON event data arrays to extract base transaction fees from the second array element and transaction tips from the third array element. Combine these amounts to calculate total transaction fees per extrinsic. Convert fee amounts from the native 18-decimal blockchain format to standard decimal representation by dividing by 10^18.
- **Key fields**: `event_pallet`, `event_method`, `event_data` arrays containing fee amounts, `extrinsic_id` for transaction identification, `transaction_fee` and `transaction_tip` extracted amounts

### Component B: USD conversion
- **Purpose**: Convert native Energy Web token fees to USD values for standardized revenue calculation
- **Logic**: Join the processed fee data with end-of-day price feeds from CoinGecko for the energy-web-token. Apply the daily closing prices to convert native token amounts to USD equivalents. This ensures consistent currency representation across different time periods and enables comparison with other blockchain protocols.
- **Key fields**: `coingecko_id` set to 'energy-web-token', daily closing prices, converted USD fee amounts

### Component C: Daily active user calculation
- **Purpose**: Count unique transaction senders per day to determine the active user base
- **Logic**: Extract transaction sender addresses from Energy Web extrinsic records, filtering to identify unique users who submitted transactions each day. Classify these users as 'Transaction sender' user type within the 'blockchains_l2' market sector and 'blockchain' business segment. Use HyperLogLog sketching algorithms to efficiently count distinct users across multiple dimensional breakdowns including project-level, chain-level, user-type-level, and product-level aggregations.
- **Key fields**: `user_address` from sender identification, `block_timestamp` for daily aggregation, `user_type` classification, HyperLogLog sketches for distinct counting

### Component D: Revenue calculation
- **Purpose**: Calculate net protocol revenue by accounting for supply-side fee distributions
- **Logic**: Take the total USD-converted transaction fees and subtract any supply-side fees that are distributed to network participants rather than retained by the protocol. For Energy Web, supply-side fees are set to zero, meaning all transaction fees count as protocol revenue. This reflects Energy Web's fee model where the entire fee amount contributes to protocol revenue.
- **Key fields**: Total daily `fees` from fee extraction, `fees_supply_side` (always zero for Energy Web), net `revenue` calculation

### Final aggregation
- **Combining components**: Join the daily revenue data with the daily active user counts on matching date boundaries. Both datasets are aggregated to daily granularity with consistent timestamp alignment to ensure accurate ratio calculations.
- **Currency conversion**: All revenue amounts are expressed in USD based on end-of-day CoinGecko prices for energy-web-token, providing standardized monetary values across time periods.
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with missing days filled with zero values to maintain complete time series continuity.
- **Final calculation**: Calculate ARPU by dividing the total daily revenue in USD by the count of daily active users for each date. The result represents the average revenue generated per active user on that specific day. Apply data quality filters and standardization through finalization macros to ensure consistent schema and complete time series coverage.

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

Energy Web XEWT

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape