Validators process transactions and receive fees from users (supply-side fees).

Astar is a collective driving web3 adoption by connecting people through blockchain technology, business innovation, decentralized applications, and seamless digital experiences in the Polkadot ecosystem. Astar was founded by Sota Watanabe and launched in 2021.

ASTR tokenholders own and govern the protocol. Part of the transaction fees is burned (revenue). Astar’s investors include Binance, Polychain Capital, Crypto.com, etc.

website

twitter

github

discord

Blockchains (L2)

Astar

# Astar Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the average daily revenue generated per active user on the Astar network. This metric is calculated by dividing total daily protocol revenue by the number of daily active users. The calculation accounts for both Layer 1 (native Astar) and Layer 2 (AstarEVM) activity, providing a comprehensive view of revenue efficiency across the entire Astar ecosystem. ARPU helps assess the monetization effectiveness and user value generation of the protocol.

## 2. Data sources

The ARPU calculation relies on several key data sources:

- **Astar blockchain events**: Parsed event logs from the Astar blockchain containing transaction fee payments, balance withdrawals, and deposits
- **Astar blockchain extrinsics**: Native Astar transaction records containing sender information and execution details  
- **AstarEVM transaction data**: Ethereum-compatible transaction records for Layer 2 activity via `Executed` events
- **End-of-day price feeds**: Token price data from CoinGecko for ASTR token USD conversion
- **Chain availability metadata**: Data defining operational periods for accurate metric calculation

## 3. Step-by-step calculation

### Component A: Layer 1 fee collection
- **Purpose**: Extract transaction fees from native Astar blockchain transactions
- **Logic**: Process `TransactionFeePaid` events from the `transactionPayment` pallet. Each event contains transaction fees and tips paid by users. The total fee is calculated as the sum of `transaction_fee` and `transaction_tip` fields extracted from the event data array. Fees are normalized from wei units to token units by dividing by 10^18.
- **Key fields**: `transaction_fee`, `transaction_tip`, `extrinsic_id`, `timestamp`

### Component B: Layer 2 fee collection  
- **Purpose**: Calculate net fees from AstarEVM (Layer 2) transactions
- **Logic**: Process balance `Withdraw` and `Deposit` events from the `balances` pallet within ethereum transactions. Withdraw events represent fee payments (positive values) while Deposit events represent refunds (negative values). Only include transactions where the signer address matches between the main extrinsic and the balance events. Aggregate net fees per extrinsic and normalize from wei to token units.
- **Key fields**: `transaction_fee`, `signer_address`, `extrinsic_id`, `event_method`

### Component C: User identification
- **Purpose**: Count unique daily active users across both layers
- **Logic**: Identify users from two sources: native Astar extrinsics (using the `id` field as user address) and AstarEVM transactions (extracting addresses from `Executed` events in the ethereum pallet). Deduplicate users within each day using HyperLogLog aggregation to handle users active on both layers. Users are categorized as "Transaction sender" type.
- **Key fields**: `user_address`, `block_timestamp`, `chain`, `user_type`

### Component D: Revenue calculation
- **Purpose**: Convert native token fees to USD revenue
- **Logic**: Combine Layer 1 and Layer 2 fees into total daily fees per chain. Convert ASTR token fees to USD using end-of-day CoinGecko price feeds. All collected fees are treated as protocol revenue since Astar retains transaction fees as its primary revenue source.
- **Key fields**: `fees`, `coingecko_id`, `daily_timestamp`

### Final aggregation
- **Combining components**: Revenue data is aggregated by day across both chains (astar and astarevm), while user data is similarly aggregated with HyperLogLog deduplication across chains and user types
- **Currency conversion**: Native ASTR token amounts are converted to USD using CoinGecko end-of-day price feeds matched by timestamp
- **Time aggregation**: All data is truncated to daily boundaries using `timestamp_trunc(block_timestamp, day)` for consistent aggregation
- **Final calculation**: ARPU is calculated by dividing total daily revenue (in USD) by the total daily active user count using the `calculate_arpu` macro, which handles the division and applies appropriate formatting and validation rules

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

AstarASTR

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape