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 Revenue Methodology

## 1. Overview

Heima revenue represents the total transaction fees collected by the Heima network from both Layer 1 (parachain) and Layer 2 (EVM) operations. The metric captures fees paid by users for executing transactions on the Heima blockchain infrastructure, including base transaction fees and tips on L1, and gas fees for EVM operations on L2. This provides insight into the network's fee revenue generation and usage patterns across both execution environments.

## 2. Data sources

- **Heima blockchain event logs**: Primary source containing all on-chain events including transaction fee payments, account creations, and EVM executions
- **Transaction execution events**: Parsed `TransactionFeePaid` events from L1 operations and `Executed` events from L2 EVM operations
- **Balance transfer events**: `Withdraw` and `Deposit` balance events associated with L2 transaction fee processing
- **Account creation events**: `NewAccount` system events used to establish parachain account mappings
- **End-of-day price feeds**: CoinGecko price data for Heima token to enable USD conversion

## 3. Step-by-step calculation

### Component A: Layer 1 fee collection
- **Purpose**: Captures transaction fees from native Heima parachain operations
- **Logic**: Extracts successful `TransactionFeePaid` events from Heima blockchain event logs. For each event, retrieves the base transaction amount from the second data field and tip amount from the third data field. Converts both values from wei to native token units by dividing by 1e18. Sums the base amount and tip to get total fee per transaction. Aggregates all fees daily by grouping transactions by day, chain, and product identifier.
- **Key fields**: `amount` (base transaction fee), `tip` (additional user tip), `block_timestamp` (transaction timing), `success` flag (transaction status)

### Component B: Account mapping for Layer 2 attribution
- **Purpose**: Creates mapping between parachain accounts and EVM addresses to properly attribute L2 fees
- **Logic**: Processes `NewAccount` system events to extract parachain account identifiers. Applies custom JavaScript function to convert substrate-format addresses to hexadecimal representation. Derives corresponding EVM addresses by concatenating "evm:" prefix with substrate hex, computing keccak256 hash, and taking the last 20 bytes as the EVM address. This enables linking parachain signers to their EVM operations.
- **Key fields**: `parachain_account` (original substrate address), `evm_account` (derived EVM address)

### Component C: Layer 2 fee collection  
- **Purpose**: Captures transaction fees from EVM operations on Heima L2
- **Logic**: First identifies EVM users by extracting `Executed` events from the EVM pallet, capturing signer addresses and transaction identifiers. Then collects corresponding balance events - `Withdraw` events (positive amounts representing fees paid) and `Deposit` events (negative amounts representing refunds) from the balances pallet for ethereum transactions. Joins these datasets with the account mapping to ensure only fees where the balance event signer matches the EVM execution signer are included. Nets withdraw and deposit amounts per transaction to get final fee amount. Converts from wei to native tokens and aggregates daily.
- **Key fields**: `signer_address` (transaction signer), `transaction_fee` (net fee amount), `extrinsic_id` (transaction identifier)

### Final aggregation
- **Combining components**: Unions L1 fees and L2 fees into a single dataset, with both components aggregated daily and labeled with 'heimachain' as the product identifier
- **Currency conversion**: Applies USD conversion using end-of-day Heima token prices from CoinGecko, matching fees to prices by date
- **Time aggregation**: All fees are aggregated to daily granularity using day-truncated timestamps
- **Final calculation**: The final revenue value represents the sum of all L1 and L2 transaction fees converted to USD, with any missing days filled forward and chain availability filters applied

*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.

HeimaHEI

Revenue

Revenue

Competitive landscape

Chain breakdown