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

## 1. Overview

Supply-side fees represent the portion of transaction fees that are distributed back to token holders, liquidity providers, or other stakeholders rather than being burned or paid to validators. For Heima, this metric is consistently zero, indicating that the protocol does not implement any fee-sharing mechanism with token holders. All transaction fees collected on both the substrate (L1) and EVM (L2) layers of Heima are retained by the network for validator rewards and operational expenses.

## 2. Data sources

- **Heima parachain event logs**: Parsed blockchain events from the Heima parachain including `TransactionFeePaid`, `evm.Executed`, balances Withdraw, balances Deposit, and `system.NewAccount` events
- **CoinGecko price feeds**: End-of-day price data for the LIT token used for USD conversion
- **Account mapping data**: Substrate to EVM address mappings derived from parachain account creation events

## 3. Step-by-step calculation

### Component A: L1 (substrate) fee extraction
- **Purpose**: Captures base transaction fees and tips paid on the Heima parachain substrate layer
- **Logic**: Extracts successful `TransactionFeePaid` events from Heima parachain logs. Parses the `amount` field (base transaction fee) and `tip` field (additional tip) from the event data arrays. Converts amounts from the smallest token unit to whole tokens by dividing by 1e18. Aggregates fees by day, extrinsic hash, and event index to avoid double counting
- **Key fields**: `amount` (base transaction fee), `tip` (additional validator tip), `block_timestamp`, `extrinsic_hash`, `success` status

### Component B: L2 (EVM) fee extraction  
- **Purpose**: Captures transaction fees paid on the EVM layer of Heima parachain
- **Logic**: Identifies EVM transactions through `evm.Executed` events that contain the transaction signer address. Matches these with corresponding balances Withdraw events (fees paid) and balances Deposit events (refunds) from the ethereum pallet. Uses account mapping to ensure the signer of withdraw/deposit events matches the EVM transaction executor. Calculates net transaction fees by summing withdrawals and subtracting deposits for each extrinsic. Aggregates by day and extrinsic ID
- **Key fields**: `signer_address` (transaction executor), `transaction_fee` (net fee amount), `extrinsic_id`, `event_method` (Withdraw or Deposit)

### Component C: Account mapping
- **Purpose**: Links substrate parachain accounts to their corresponding EVM addresses for proper fee attribution
- **Logic**: Processes `system.NewAccount` events to extract parachain account addresses. Converts substrate addresses to hex format, then derives EVM addresses using keccak256 hashing with the "evm:" prefix. This mapping ensures L2 fees are correctly attributed to the same entity across both layers
- **Key fields**: `parachain_account` (substrate address), `evm_account` (derived EVM address)

### Final aggregation
- **Combining components**: L1 fees (amount plus tip) and L2 fees (net transaction costs) are combined into daily totals for the 'heimachain' product on the 'heima' chain
- **Currency conversion**: Native LIT token amounts are converted to USD using end-of-day CoinGecko price feeds for the 'heima' token identifier
- **Time aggregation**: All fees are aggregated to daily boundaries using timestamp truncation to day level
- **Final calculation**: The supply-side fees value is set to zero for all records, indicating that Heima does not distribute any portion of collected fees to token holders or liquidity providers. The total fees collected are tracked separately but none are classified as supply-side

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

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

HeimaHEI

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown