Build once, connect everywhere. Hyperbridge gives developers the secure infrastructure to scale applications across any network.

website

twitter

github

discord

Bridges

Hyperbridge

# Hyperbridge Average fees per user (AFPU) Methodology

## 1. Overview

Average fees per user (AFPU) measures the fees paid per active user over a fixed 24-hour window. It is calculated as total daily fees divided by active users (daily), and reflects how much an individual user pays for the project’s service on a daily basis. Insight into user monetization efficiency across both Hyperbridge Substrate and Hyperbridge App is provided by this metric.

## 2. Data sources

- **Fees**: Derived from the Fees metric
- **Active users (daily)**: Derived from the Active users (daily) metric

## 3. Step-by-step calculation

### Component A: Hyperbridge Substrate and Hyperbridge App active users (daily)

- **Purpose**: Distinct active users across the Hyperbridge ecosystem are identified and counted.
- **Logic**: User addresses are extracted from direct users of Hyperbridge Substrate and users of Hyperbridge App across multiple EVM chains. For Hyperbridge Substrate, sender addresses are extracted from extrinsic records. For Hyperbridge App, transaction sender addresses are extracted from transaction records on Arbitrum, Ethereum, Optimism, Base, BSC, Gnosis, Polygon, and Unichain. Transactions are filtered to include only those sent to predefined contract addresses, including Host, Handler, IntentGateway, and TokenGateway. User addresses are deduplicated and grouped by day to calculate active users (daily).
- **Key fields**: `user_address` (user identifier), `block_timestamp` (timing), `from_address` (transaction sender), `to_address` (contract address), `id` (extrinsic sender)

### Component B: Hyperbridge Substrate fee collection

- **Purpose**: Transaction fees paid on Hyperbridge Substrate are collected.
- **Logic**: `TransactionFeePaid` events are extracted from Hyperbridge Substrate event data. Fee and tip amounts are extracted in the native Hyperbridge asset, normalized by decimal precision, and summed to obtain total transaction fees. Fees are grouped by day and converted to USD using end-of-day asset price feeds.
- **Key fields**: `amount` (base transaction fee), `tip` (additional tip), `block_timestamp` (timing)

### Component C: Hyperbridge App fee collection

- **Purpose**: Relayer and messaging fees from Hyperbridge App operations are collected.
- **Logic**: `AccumulateFees` events from `relayer` pallets and `FeePaid` events from `messagingFees` pallets are extracted from Hyperbridge Substrate event data. Fees paid in the DAI asset for processing cross-chain messages are tracked by these events. Fee amounts are normalized by decimal precision and grouped by day. Since fees are denominated in DAI, they are treated as equivalent to USD and do not require further currency conversion.
- **Key fields**: `amount` (fee amount), `block_timestamp` (timing)

### Component D: Average fees per user (AFPU) calculation

- **Purpose**: Fee and user metrics are combined to calculate the average fees paid per user.
- **Logic**: Daily fees from Hyperbridge Substrate and Hyperbridge App are summed to calculate total daily fees. Active users (daily) from both products are aggregated and deduplicated. Average fees per user (AFPU) is calculated by dividing total daily fees by active users (daily). Missing days are filled with zeros to maintain a continuous time series.
- **Key fields**: `fees` (total daily fees), `user_dau` (active users (daily))

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

HyperbridgeBRIDGE

Archived

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape