# Hyperbridge App Revenue Methodology

## 1. Overview

Revenue measures the portion of fees that Hyperbridge App retains in its protocol treasury. This metric represents the protocol's take rate from cross-chain activity, reflecting the earnings processed through the bridge before operating expenses or incentives are deducted. Revenue is tracked by monitoring native asset inflows to the designated Hyperbridge treasury address.

## 2. Data sources

- **Blockchain events**: `Transfer` events from `balances` pallet on Hyperbridge
- **External data**: End-of-day price feeds for assets

## 3. Step-by-step calculation

### Component A: Treasury transfer identification

- **Purpose**: Identify asset transfers specifically directed to the protocol treasury.
- **Logic**: `Transfer` events from the `balances` pallet are parsed to identify all successful movements of assets. These transfers are filtered to include only transactions where the recipient address matches the official Hyperbridge treasury address (`13UVJyLkyUpEiXBx5p776dHQoBuuk3Y5PYp5Aa89rYWePWA3`).
- **Key fields**: `to_address` (recipient identification), `amount` (quantity of assets transferred), `block_timestamp` (event timing).

### Component B: Data filtering and normalization

- **Purpose**: Clean the dataset to ensure only protocol-generated revenue is captured and values are mathematically consistent.
- **Logic**: Transfers originating from specific excluded addresses, such as the founder's address, are removed from the dataset to prevent the inclusion of non-revenue funding. All identified revenue amounts are normalized by decimal precision to account for the asset's underlying format on the Hyperbridge Substrate.
- **Key fields**: `from_address` (sender identification), `amount` (normalized quantity).

### Component C: USD conversion and aggregation

- **Purpose**: Convert native asset values into USD for standardized reporting.
- **Logic**: The daily sum of normalized revenue amounts is calculated at the end of each UTC day. These values are multiplied by end-of-day price feeds for the native Hyperbridge asset to determine the total USD value. Results are aggregated at a daily granularity.

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

Revenue

Bridges

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

Hyperbridge App

Archived

Revenue

Revenue

Chain breakdown