Immutable zkEVM batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Immutable zkEVM is an L2 smart contract platform for decentralized applications on Ethereum. Immutable zkEVM was founded by the Immutable team and launched in 2023.

Immutable team owns and governs the protocol. Immutable's investors include Coinbase Ventures, Temasek, Tencent Holdings, etc.

website

twitter

github

telegram

discord

medium

governance

etherscan

Blockchains (L2)

Immutable zkEVM

# Immutable zkEVM Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the daily revenue generated per active user on the Immutable zkEVM blockchain. This metric answers the question: "How much revenue does each user generate on average per day?" The calculation divides total daily revenue (derived from gas fees) by the number of daily active users, providing insight into the economic value generated by the user base.

## 2. Data sources

The calculation relies on these raw data sources:

- **Blockchain transaction data**: Immutable zkEVM transaction records containing transaction details, gas usage, gas prices, sender/receiver addresses, and timestamps
- **Wallet event data**: Immutable v1 Passport `NonceChange` events that identify additional wallet users beyond transaction senders
- **External price data**: End-of-day token price feeds for ETH to enable USD conversion of gas fees
- **Token metadata**: Immutable zkEVM native token information including the IMX token address (`0xf57e7e7c23978c3caec3c3548e3d615c346e79ff`)

## 3. Step-by-step calculation

### Component A: Gas fee calculation
- **Purpose**: Calculate the gas fees paid for each transaction on Immutable zkEVM
- **Logic**: Extract transaction records from Immutable zkEVM blockchain data. For each transaction, calculate the total gas fee by multiplying `gas_used` by `effective_gas_price`. The `effective_gas_price` is converted from wei to ETH by dividing by 10^18. This produces the gas fee amount in ETH for each transaction.
- **Key fields**: `gas_used` (gas consumed), `effective_gas_price` (price per gas unit in wei), `gas_fee` (calculated fee in ETH), `block_timestamp`, `transaction_hash`, `from_address`

### Component B: Revenue aggregation  
- **Purpose**: Convert gas fees to USD and aggregate to daily revenue totals
- **Logic**: Take the calculated gas fees from Component A and convert them from ETH to USD using end-of-day price feeds. Group transactions by day (truncating `block_timestamp` to day boundaries) and sum all gas fees to get total daily revenue. The chain ID is initially set to 'ethereum' for price conversion, then changed back to 'immutablezkevm' for final output.
- **Key fields**: `timestamp` (day boundary), `fees` (gas fees in USD), `chain_id`, `product_id` ('immutablezkevm')

### Component C: User identification
- **Purpose**: Identify all unique users active on each day across multiple user types
- **Logic**: Combine users from two sources: (1) transaction senders from Immutable zkEVM transactions, classified as 'Transaction sender' user type, and (2) wallet addresses from Immutable v1 Passport `NonceChange` events, classified as 'Passport wallet user' type. Each user record includes the user address, timestamp, and user type classification.
- **Key fields**: `user_address`, `block_timestamp`, `user_type`, `chain` ('immutablezkevm'), `product_id`

### Component D: Daily active user aggregation
- **Purpose**: Count unique daily active users across all user types
- **Logic**: Group user data by day (truncating `block_timestamp` to day boundaries) and count distinct user addresses using HyperLogLog algorithm for accurate distinct counting. This handles users who may appear in multiple user type categories by ensuring they are only counted once per day. Create breakdowns by project level, chain level, user type level, and product level using HyperLogLog merge operations.
- **Key fields**: `timestamp` (day boundary), `user_dau` (distinct user count), `dimensions` (breakdown level), `chain_id`, `user_type`

### Final aggregation
- **Combining components**: The ARPU calculation uses the `calculate_arpu` macro which divides the daily revenue totals from Component B by the daily active user counts from Component D. Revenue data is joined with user data on timestamp and relevant dimensional keys.
- **Currency conversion**: All revenue values are converted to USD using end-of-day price feeds before the ARPU calculation
- **Time aggregation**: Both revenue and user metrics use day-level time boundaries created by truncating timestamps to day granularity
- **Final calculation**: ARPU = Daily Revenue (USD) ÷ Daily Active Users. The result shows the average revenue generated per user per day. Days with no users or no revenue are filled with zeros using the 'fill_zeros' strategy to maintain complete time series data.

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

Immutable zkEVMIMX

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape