deBridge operates two main products: (1) deBridge Messaging - node operators validate cross-chain transactions for data and asset transfers, and (2) DLN (deBridge Liquidity Network) - an order book of cross-chain intents where Makers create intents in the source chain and Takers provide liquidity on the destination chain. Validators currently do not take a cut of transfer fees (supply-side fees).

deBridge is an interoperability protocol with two products: deBridge Messaging enables decentralized transfers of data and assets between blockchains, and DLN (deBridge Liquidity Network) is a cross-chain token bridge and trading infrastructure. deBridge was founded by Alex Smirnov and launched in 2021, with DLN launched in 2023.

The deBridge team and investors own and govern the protocol. They currently take all transfer fees paid by traders (revenue). deBridge's investors include ParaFi Capital, Animoca Brands, Huobi Ventures, Lemniscap, etc. All fees paid by traders are accumulated on smart contracts operated by the deBridge team and will be governed by deBridge token holders.

github

twitter

discord

website

Interoperability

deBridge

# deBridge Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the average daily revenue generated per active user on the deBridge Messaging protocol. deBridge Messaging is a cross-chain interoperability protocol that enables asset transfers between different blockchain networks. The metric is calculated by dividing total daily revenue (from bridge fees) by the number of daily active users, providing insight into user monetization efficiency across the deBridge Messaging ecosystem.

## 2. Data sources

- **Cross-chain bridge events**: Parsed `DeBridgeGate_Sent_event` logs from Ethereum, Arbitrum, Avalanche, Base, BSC, Fantom, Optimism, and Polygon networks containing transfer details, fee information, and user addresses
- **Asset mapping events**: Parsed `DeBridgeGate_PairAdded_event` logs from the same chains providing mappings between deBridge Messaging asset IDs and native token addresses
- **Token pricing data**: End-of-day token price feeds for USD conversion of fees across all supported tokens
- **Token metadata**: Token contract information including decimal places and symbols for proper amount calculations

## 3. Step-by-step calculation

### Component A: Asset ID mapping
- **Purpose**: Creates a mapping between deBridge Messaging internal asset IDs and actual token addresses across different chains
- **Logic**: Extracts asset mappings from `DeBridgeGate_PairAdded_event` logs across all eight supported chains. For each event, captures the `debridgeId`, `nativeChainId`, and `nativeAddress` fields. Matches the `nativeChainId` numeric values to chain names (e.g., '1' to 'ethereum', '42161' to 'arbitrum'). Removes duplicates and null values to create a clean mapping table
- **Key fields**: `debridge_id` (internal asset identifier), `native_token_chain` (source blockchain), `native_token_address` (actual token contract address)

### Component B: Transfer fee extraction
- **Purpose**: Extracts both fixed and percentage-based fees from bridge transfer events
- **Logic**: Processes `DeBridgeGate_Sent_event` logs across all supported chains to extract two types of fees. Fixed fees (`fixFee` field) are flat fees denominated in the blockchain's native token (ETH, AVAX, etc.). Transfer fees (`transferFee` field) are percentage-based fees denominated in the token being bridged. Uses the asset mapping to link `debridgeId` values to actual token addresses. Each fee type is processed separately through decimal correction and USD conversion
- **Key fields**: `fixed_fee_amount` (flat fee in native tokens), `transfer_fee_amount` (percentage fee in bridged tokens), `account_address` (user performing the transfer)

### Component C: Fee processing and aggregation
- **Purpose**: Converts raw fee amounts to standardized USD values and combines all fee types
- **Logic**: Applies decimal correction using token metadata to convert raw blockchain amounts to actual token amounts. Converts all fees to USD denomination using end-of-day price feeds matched by date and token address. Combines fixed fees and transfer fees into a single revenue stream. Aggregates fees by day, chain, and other dimensions. All fees accrue to the deBridge Messaging treasury and are treated as 100% revenue
- **Key fields**: `fees` (USD-denominated fee amounts), `timestamp` (daily aggregation), `chain_id` (blockchain identifier)

### Component D: Daily active user calculation
- **Purpose**: Counts unique daily active users across the deBridge Messaging protocol
- **Logic**: Extracts user addresses from the `nativeSender` field in `DeBridgeGate_Sent_event` logs across all chains. Identifies users as "Sender" type based on their bridge transfer activity. Uses HyperLogLog (HLL) sketches for efficient unique user counting across large datasets. Aggregates users by multiple dimensions including total protocol level, individual chains, user types, and products. Removes duplicates to ensure each user is counted only once per day regardless of transaction volume
- **Key fields**: `user_address` (unique user identifier), `user_type` (classification as "Sender"), `chain` (blockchain where activity occurred)

### Final aggregation
- **Combining components**: Revenue data (daily fee totals in USD) is matched with user data (daily unique user counts) by date and other shared dimensions. The ARPU calculation macro divides total daily revenue by total daily active users for each day
- **Currency conversion**: All fees are converted to USD using end-of-day price feeds, ensuring consistent revenue measurement across different tokens and chains
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation. Missing days are filled with zero values to maintain complete time series
- **Final calculation**: ARPU = Total Daily Revenue (USD) ÷ Total Daily Active Users. The result represents the average revenue generated per active user on each day across the entire deBridge Messaging protocol

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

deBridgeDBR

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape