IoTeX is the blockchain platform for Real-World AI. Since 2017, its foundational infrastructure has delivered verified, real-time data from the real world to AI systems and decentralized applications. Powering 100+ projects and 40M devices across mobility, robotics, energy, health, and more, IoTeX enables developers to build next-gen AI models and applications that deliver real-world impact. The IoTeX tech stack provides the data, identity, and verification layers to fulfill the surging demand for real-world data in the new AI era. Trusted by partners like Google, Samsung, IEEE, ARM, and Nordic Semiconductor, IoTeX is uniquely positioned to capture the multi-trillion-dollar AI and data economy.

website

twitter

github

discord

Blockchains (L1)

IoTeX

# IoTeX Revenue Methodology

## 1. Overview

The IoTeX revenue metric measures the daily protocol revenue generated by the IoTeX blockchain. This metric combines two primary revenue sources: base fees (the portion of transaction fees that are burned) and blob fees (fees paid for blob data storage). The metric represents the actual value captured by the protocol from network usage, calculated by aggregating transaction-level fee data and converting to USD.

## 2. Data sources

The calculation relies on these underlying data sources:
- **IoTeX blockchain block data**: Block-level information including base fee per gas rates, total gas used per block, block numbers, and timestamps
- **IoTeX blockchain transaction data**: Individual transaction records containing gas usage, blob gas usage, gas prices, effective gas prices, blob gas prices, sender and receiver addresses, and transaction hashes
- **End-of-day token price feeds**: USD conversion rates for IOTX tokens used to convert native token amounts to USD values

## 3. Step-by-step calculation

### Component A: Base fee calculation
- **Purpose**: Calculates the base fees that are burned from each transaction, representing core protocol revenue
- **Logic**: For each transaction, multiply the `gas_used` by the `base_fee_per_gas` from the corresponding block. The base fee represents the minimum fee required for transaction inclusion and is burned rather than paid to validators. Transaction data is joined with block data using `block_number` to access the base fee rate. Gas prices are converted from wei to IOTX by dividing by 10^18. The calculation handles the EIP-1559 transition at block 33730921, using `gas_price` for earlier blocks and `receipt_effective_gas_price` for later blocks.
- **Key fields**: `gas_used`, `base_fee_per_gas`, `base_fee_amount`, `block_number`, `transaction_hash`

### Component B: Blob fee calculation  
- **Purpose**: Calculates fees paid for blob data storage, representing additional protocol revenue from data availability
- **Logic**: For each transaction that uses blob gas, multiply `blob_gas_used` by `blob_gas_price` to determine the total blob fee paid. Blob gas is used for storing large amounts of data and incurs separate fees from regular transaction gas. Only transactions with blob gas usage contribute to this component.
- **Key fields**: `blob_gas_used`, `blob_gas_price`, `blob_fee_amount`, `transaction_hash`

### Component C: Daily aggregation
- **Purpose**: Aggregates transaction-level fees to daily totals for both base fees and blob fees
- **Logic**: Group all base fee transactions by day using timestamp truncation and sum the `base_fee_amount` values. Separately, group all blob fee transactions by day and sum the `blob_fee_amount` values. Each component produces a daily time series with `timestamp`, `timestamp_grain` set to 'day', and the respective fee total.
- **Key fields**: `timestamp`, `timestamp_grain`, aggregated fee amounts

### Final aggregation
- **Combining components**: The daily base fee totals and daily blob fee totals are unioned together into a single dataset, with each row representing one fee type for one day. Both components are tagged with consistent metadata including `market_sector_id` as 'blockchains_l1', `business_segment_id` as 'blockchain', `chain_id` as 'iotex', and `token_address` as 'native'.
- **Currency conversion**: Native IOTX token amounts are converted to USD using end-of-day price feeds through the standard conversion macro, which handles decimal correction and applies appropriate exchange rates.
- **Time aggregation**: Daily boundaries are determined using timestamp truncation to day level, ensuring consistent 24-hour periods for revenue calculation.
- **Final calculation**: The final revenue metric represents the sum of base fees and blob fees for each day, converted to USD. This represents the total value captured by the IoTeX protocol from network usage and data storage fees.

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

IoTeXIOTX

Archived

Revenue

Revenue

Competitive landscape