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 Supply-side fees Methodology

## 1. Overview

Supply-side fees represent the portion of transaction fees that goes to network participants (validators/block producers) rather than being burned. For IoTeX, this metric is calculated by subtracting the burned fees (revenue) from total transaction fees. The result shows how much fee revenue is distributed to network operators, providing insight into the economic incentives for securing the IoTeX blockchain.

## 2. Data sources

The calculation uses the following raw data sources:
- **IoTeX blockchain transaction records**: Contains gas usage, gas prices, blob gas usage, and blob gas prices for each transaction
- **IoTeX blockchain block records**: Contains base fees per gas for each block 
- **End-of-day IOTX token price feeds**: Used for USD conversion of native token amounts
- **Token metadata**: Provides decimal precision information for the native IOTX token

## 3. Step-by-step calculation

### Component A: Transaction fee data extraction
- **Purpose**: Extract and process raw transaction data with gas and fee information
- **Logic**: Extract transaction records from IoTeX blockchain including gas usage (`receipt_gas_used`), blob gas usage (`receipt_blob_gas_used`), effective gas prices, and blob gas prices. Apply different gas price logic based on EIP-1559 activation at block 33730921 - use `gas_price` for earlier blocks and `receipt_effective_gas_price` for later blocks. Convert all price values from wei to IOTX by dividing by 10^18.
- **Key fields**: `gas_used`, `blob_gas_used`, `effective_gas_price`, `blob_gas_price`, `block_timestamp`

### Component B: Block data extraction  
- **Purpose**: Extract base fee information from block data
- **Logic**: Extract block records containing base fees per gas (`base_fee_per_gas`) and convert from wei to IOTX by dividing by 10^18. This base fee represents the portion of transaction fees that gets burned.
- **Key fields**: `base_fee_per_gas`, `block_number`

### Component C: Base fee calculation
- **Purpose**: Calculate the amount of fees burned per transaction
- **Logic**: Join transaction data with block data on block number. Calculate base fee amount as `gas_used` multiplied by `base_fee_per_gas` for each transaction. This represents the burned portion of transaction fees.
- **Key fields**: `base_fee_amount`

### Component D: Blob fee calculation
- **Purpose**: Calculate blob fees which are also burned
- **Logic**: For transactions with blob gas usage, calculate blob fee amount as `blob_gas_used` multiplied by `blob_gas_price`. These fees are also burned and contribute to revenue.
- **Key fields**: `blob_fee_amount`

### Component E: Total fee calculation
- **Purpose**: Calculate total fees paid by users
- **Logic**: For each transaction, calculate total fee as (`gas_used` * `effective_gas_price`) + (`blob_gas_used` * `blob_gas_price`). Handle cases where blob gas usage is null by using coalesce with 0.
- **Key fields**: `fee_amount`

### Component F: Daily aggregation
- **Purpose**: Aggregate fee data to daily totals
- **Logic**: Truncate timestamps to day granularity and sum base fee amounts, blob fee amounts, and total fee amounts separately by day. Create separate daily aggregates for each fee type.
- **Key fields**: `timestamp`, `base_fee_amount`, `blob_fee_amount`, `fees`

### Component G: Revenue calculation  
- **Purpose**: Calculate total burned fees (revenue) 
- **Logic**: Union base fee amounts and blob fee amounts, then sum them together. Both base fees and blob fees are burned and contribute to protocol revenue. Convert to USD using end-of-day IOTX price feeds.
- **Key fields**: `revenue`

### Component H: Total fees USD conversion
- **Purpose**: Convert total fees to USD
- **Logic**: Apply USD conversion to daily total fee amounts using end-of-day IOTX price feeds. No decimal correction is needed as amounts are already in IOTX.
- **Key fields**: `fees`

### Final aggregation
- **Combining components**: Union the revenue data (with negated values) and total fees data, then sum them together. The negative revenue cancels out the burned portion from total fees.
- **Currency conversion**: All IOTX amounts are converted to USD using end-of-day price feeds before final calculation
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation
- **Final calculation**: Supply-side fees = Total fees - Revenue (burned fees). This is achieved by unioning negated revenue with positive total fees and summing the result.

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

Portion of fees distributed to service providers or supply-side participants.

IoTeXIOTX

Archived

Supply-side fees

Supply-side fees

Competitive landscape