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

Unique Network is a blockchain specialized for NFTs powered by Polkadot Relay chain.

UNQ holders own and govern the protocol. Unique Network’s investors include Outlier Ventures, Animoca Brands, etc.

website

github

twitter

discord

etherscan

Blockchains (L2)

Unique Network

# Unique Network Average fees per user (AFPU) Methodology

## 1. Overview

The Average Fees Per User (AFPU) metric measures the average amount of fees paid per daily active user on the UniqueNetwork blockchain ecosystem. This metric is calculated by dividing the total daily fees collected across both Layer 1 (substrate) and Layer 2 (EVM) components by the total number of daily active users. The metric provides insight into user monetization and network usage efficiency, answering the business question: "How much revenue does the network generate per active user?"

## 2. Data sources

The calculation draws from several key data sources within the UniqueNetwork ecosystem:

- **UniqueNetwork blockchain events**: Parsed blockchain events including system account creation events, treasury deposits, balance transfers, and EVM execution logs
- **UniqueNetwork transaction data**: Layer 1 extrinsic records containing transaction metadata and signer information  
- **EVM transaction events**: Layer 2 transaction execution events from the embedded Ethereum Virtual Machine
- **Balance change events**: Withdraw and deposit events from the balances pallet during EVM transactions
- **Treasury events**: Deposit events to the treasury pallet representing collected network fees
- **External price data**: End-of-day price feeds from CoinGecko for the unique-network token to enable USD conversion
- **Account mapping data**: System-generated events for mapping between substrate and EVM address formats

## 3. Step-by-step calculation

### Component A: Daily active user tracking

- **Purpose**: Identifies and counts unique daily active users across both Layer 1 and Layer 2 networks
- **Logic**: User activity is tracked from two primary sources. For Layer 1, unique users are identified from extrinsic signers in the transaction records. For Layer 2, users are identified from EVM execution events where the `event_pallet` is 'ethereum' or 'evm' and the `event_method` is 'Executed'. All user addresses are normalized to lowercase for consistent identification. The system uses HyperLogLog aggregation to efficiently count distinct users across multiple chains and avoid double-counting users who are active on both layers.
- **Key fields**: `user_address` from extrinsic records and `event_data[0]` from EVM execution events, `block_timestamp` for daily boundary determination, `chain` identifier to distinguish between Layer 1 and Layer 2 activity

### Component B: Address mapping between substrate and EVM formats

- **Purpose**: Creates a mapping between substrate addresses and their corresponding EVM addresses to correlate cross-layer activity
- **Logic**: The system processes `NewAccount` events from the system pallet to identify substrate addresses. Each substrate address is converted to its corresponding EVM address using a deterministic algorithm. The conversion involves decoding substrate addresses and applying a keccak256 hash with an "evm:" prefix to derive the equivalent EVM address format. This mapping ensures that users active on both layers are properly identified and their fees are correctly attributed.
- **Key fields**: `parachain_account` as the source substrate address, `evm_account` as the derived EVM address, `event_data[0]` containing the original substrate address from system events

### Component C: Layer 1 fee collection

- **Purpose**: Captures fees collected on the Layer 1 substrate chain through treasury deposits
- **Logic**: Layer 1 fees are identified from treasury deposit events where the `event_pallet` is 'treasury' and `event_method` is 'Deposit'. Only successful events are included in the calculation. The fee amount is extracted from the first element of the event data array and converted from the native token's 18-decimal precision to standard units by dividing by 1e18.
- **Key fields**: `event_data[0]` containing the fee amount in native token units, `block_timestamp` for daily aggregation, `success` flag to ensure only valid transactions are included

### Component D: Layer 2 fee calculation  

- **Purpose**: Calculates net fees paid during EVM transactions by tracking balance changes
- **Logic**: Layer 2 fees are derived from balance change events during EVM transactions. The system tracks both 'Withdraw' and 'Deposit' events from the balances pallet where the `pallet` is 'evm'. Withdrawals represent fee payments (positive values) while deposits represent refunds or change (negative values). For each transaction, the net fee is calculated by summing all withdrawals and subtracting all deposits. Only transactions where the balance change signer matches the original EVM transaction signer are included, using the address mapping to verify correlation between substrate and EVM addresses.
- **Key fields**: `transaction_fee` calculated from `event_data[1]` representing balance change amounts, `signer_address` from `event_data[0]` for transaction attribution, `extrinsic_id` for grouping related events

### Component E: Fee aggregation and USD conversion

- **Purpose**: Combines Layer 1 and Layer 2 fees and converts to USD for standardized reporting
- **Logic**: Daily fees from both layers are aggregated by summing Layer 1 treasury deposits and Layer 2 net transaction fees. The combined fee amount is then converted to USD using end-of-day price data from CoinGecko for the unique-network token. The conversion accounts for the token's decimal precision and applies the appropriate exchange rate for each day.
- **Key fields**: `fees` as the daily total in native token units, `timestamp` truncated to daily boundaries for price matching, `chain_id` and `product_id` for dimensional breakdown

### Final aggregation

- **Combining components**: The daily active user count and total daily fees are combined using the calculate_arpu macro, which performs a division operation to determine the average fees per user
- **Currency conversion**: All fee amounts are converted to USD using end-of-day CoinGecko price feeds for the unique-network token before the final division
- **Time aggregation**: Both user counts and fee totals are aggregated to daily boundaries using timestamp truncation to ensure consistent time-based matching  
- **Final calculation**: The AFPU metric is calculated as the total daily fees in USD divided by the total daily active users, producing an average revenue per user value that represents how much each active user contributes to network fees on average

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

Unique NetworkUNQ

Archived

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape