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

Heima is a specialized identity and data verification blockchain powered by Polkadot Relay chain.

HEI holders own and govern the protocol. Heima’s investors include LD Capital, Digital Renaissance, Signum Capital, and others.

website

twitter

github

discord

etherscan

Blockchains (L2)

Heima

# Heima Average fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average transaction fees paid per daily active user on the Heima blockchain. This metric answers the business question: "How much revenue does each active user generate through transaction fees?" The calculation divides total daily fees (in USD) by the number of daily active users, providing insight into user engagement value and network utilization patterns across both Heima's substrate layer (L1) and EVM compatibility layer (L2).

## 2. Data sources

- **Heima blockchain event logs**: Parsed events from Heima's substrate blockchain including `TransactionFeePaid` events for L1 fees, `NewAccount` events for account mapping, `Executed` events for EVM transactions, and `Withdraw`/`Deposit` events for L2 fee tracking
- **Heima extrinsic records**: Transaction records from Heima's substrate layer containing transaction sender information
- **Balance change events**: Substrate balance events from the ethereum pallet tracking EVM transaction costs through balance modifications  
- **Account mapping data**: Substrate account addresses and their corresponding EVM address derivations
- **End-of-day price feeds**: CoinGecko price data for the Heima token used for USD conversion of native token fees

## 3. Step-by-step calculation

### Component A: Account mapping creation
- **Purpose**: Establishes the relationship between substrate and EVM accounts for cross-layer fee attribution
- **Logic**: Extract distinct parachain accounts from substrate `NewAccount` events. Decode SS58-encoded substrate addresses to hex format using base58 decoding. Derive corresponding EVM addresses by computing the keccak256 hash of the concatenated string "evm:" plus the substrate account hex, then taking bytes 12-32 as the EVM address. This mapping enables attribution of L2 EVM fees to the correct substrate account holders.
- **Key fields**: `parachain_account` (original substrate address), `evm_account` (derived EVM address)

### Component B: Layer 1 substrate fees
- **Purpose**: Captures transaction fees from native substrate operations
- **Logic**: Extract `TransactionFeePaid` events from successful substrate extrinsics. Parse fee components including base transaction amount and optional tip from the event data payload. Convert amounts from 18-decimal native token units to standard decimal format. Aggregate fees by day, block, and extrinsic hash.
- **Key fields**: `amount` (base transaction fee), `tip` (optional additional fee), `extrinsic_hash` (transaction identifier)

### Component C: Layer 2 EVM fees  
- **Purpose**: Tracks transaction costs for EVM operations on Heima's EVM compatibility layer
- **Logic**: Identify EVM transactions through ethereum pallet `Executed` events to get transaction executors. Extract corresponding balance `Withdraw` events (positive fees) and `Deposit` events (negative refunds) from the ethereum pallet. Match balance change signers to EVM transaction executors using the account mapping. Only include fees where the balance change signer corresponds to the EVM executor via the substrate-to-EVM mapping. Sum net balance changes per extrinsic to get total EVM transaction costs.
- **Key fields**: `transaction_fee` (net balance change), `signer_address` (account experiencing balance change), `extrinsic_id` (transaction reference)

### Component D: Combined fee aggregation
- **Purpose**: Consolidates L1 and L2 fees into total daily fees with USD conversion  
- **Logic**: Combine daily aggregated L1 fees (amount plus tip) and L2 fees (net transaction costs). Group by day and chain to get total native token fees. Apply end-of-day Heima token prices from CoinGecko to convert native token amounts to USD equivalent. Sum across both layers to get total daily fees in USD.
- **Key fields**: `fees` (total daily fees in USD), `chain_id` (Heima), `product_id` (heimachain)

### Component E: Daily active users
- **Purpose**: Counts distinct users active each day across both substrate and EVM layers
- **Logic**: Extract user addresses from substrate extrinsic records as transaction senders. Extract user addresses from ethereum pallet `Executed` events for EVM transactions. Combine both address types and count distinct addresses per day using HyperLogLog aggregation. Apply project-level aggregation to get total daily active users across all Heima layers.
- **Key fields**: `user_address` (distinct user identifier), `user_type` (Transaction sender), `chain` (heima or heimaevm)

### Final aggregation
- **Combining components**: The final AFPU calculation divides total daily fees (USD) by daily active users at the project level
- **Currency conversion**: Native Heima token fees are converted to USD using end-of-day CoinGecko price feeds with the 'heima' coingecko identifier  
- **Time aggregation**: All data is truncated to daily boundaries and aggregated by calendar day
- **Final calculation**: AFPU = Sum of daily L1 and L2 fees (in USD) divided by count of distinct daily active users across substrate and EVM layers

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

HeimaHEI

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape