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

website

twitter

github

discord

Bridges

Hyperbridge

# Hyperbridge Fees Methodology

## 1. Overview

The Hyperbridge fees metric measures the total daily fee revenue generated by the Hyperbridge protocol across two distinct revenue streams: chain operation fees and bridge relayer fees. This metric combines native Hyperbridge token fees from blockchain transactions with DAI-denominated fees from cross-chain bridge operations to provide a comprehensive view of protocol fee generation.

## 2. Data sources

- **Hyperbridge blockchain events**: Parsed event logs from the Hyperbridge blockchain containing transaction fee payments and bridge operations
- **Transaction fee events**: `TransactionFeePaid` events capturing native token fees and tips paid for blockchain transactions
- **Bridge fee events**: `AccumulateFees` events from the relayer pallet and `FeePaid` events from the messagingFees pallet, both denominated in DAI
- **External price data**: End-of-day price feeds from CoinGecko for Hyperbridge native token (hyperbridge-2 identifier)
- **DAI price stability**: DAI stablecoin treated as equivalent to $1 USD without additional price conversion

## 3. Step-by-step calculation

### Component A: Chain transaction fees
- **Purpose**: Captures revenue from native Hyperbridge blockchain transaction fees paid in the native token
- **Logic**: Extracts `TransactionFeePaid` events from successful transactions on the Hyperbridge blockchain. Each event contains an `amount` field for the base transaction fee and a `tip` field for additional miner incentives. Both values are converted from native token units using a divisor of 1e12 to account for token decimals. The sum of amount and tip represents the total fee paid per transaction. Daily aggregation groups all transactions by date and sums the total fees
- **Key fields**: `amount` (base transaction fee), `tip` (additional fee), `block_timestamp` (transaction timing), `success` flag (ensures only successful transactions)

### Component B: Bridge relayer fees  
- **Purpose**: Captures revenue from cross-chain bridge operations, specifically relayer fees paid in DAI stablecoin
- **Logic**: Combines two types of DAI-denominated bridge fees. First, `AccumulateFees` events from the relayer pallet track fees accumulated by bridge relayers. Second, `FeePaid` events from the messagingFees pallet capture fees paid for cross-chain message handling. All fee amounts are converted from DAI units using a divisor of 1e18 to account for standard ERC-20 token decimals. Daily aggregation sums both fee types by date
- **Key fields**: `amount` (fee value in DAI), `event_pallet` (relayer or messagingFees), `event_method` (AccumulateFees or FeePaid), `success` flag

### Final aggregation
- **Combining components**: The two fee streams are combined using a union operation, with each maintaining distinct product identifiers - chain fees labeled as 'Hyperbridge Substrate' and bridge fees as 'hyperbridge'
- **Currency conversion**: Chain fees in native Hyperbridge tokens are converted to USD using end-of-day price feeds from CoinGecko. Bridge fees remain in DAI values since DAI maintains approximate parity with USD
- **Time aggregation**: Both components aggregate to daily boundaries using timestamp truncation to day granularity
- **Final calculation**: The final metric represents the sum of USD-equivalent daily fees across both revenue streams, standardized through gap-filling to ensure continuous daily values even when no fees are collected on specific days

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

Total value users pay to use a protocol (gross fees, user-paid fees).

HyperbridgeBRIDGE

Archived

Fees

Fees

Competitive landscape

Chain breakdown