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 Transfer volume Methodology

## 1. Overview

deBridge Messaging transfer volume measures the total daily USD value of tokens transferred across chains through deBridge Messaging's interoperability infrastructure. This metric captures volume from two main products: the core deBridge Messaging protocol for general cross-chain transfers and deBridge Liquidity Network (DLN) (deBridge Messaging Liquidity Network) for liquidity-based transfers. The calculation aggregates transfer amounts from both systems, converts them to USD using end-of-day pricing, and presents daily totals across supported blockchain networks.

## 2. Data sources

The metric relies on several key data sources:
- **Bridge event logs**: Parsed `DeBridgeGate_Sent_event` logs from Arbitrum, Avalanche, Base, BSC, Ethereum, Fantom, Optimism, and Polygon capturing core bridge transfers
- **deBridge Liquidity Network (DLN) event logs**: Parsed `DlnSource_ClaimedUnlock_event` logs from the same 8 chains tracking deBridge Liquidity Network (DLN) liquidity network transfers  
- **Asset mapping events**: `DeBridgeGate_PairAdded_event` logs that establish relationships between deBridge Messaging asset IDs and their corresponding native token addresses and chains
- **End-of-day price feeds**: Token price data for USD conversion of transfer volumes
- **Token metadata**: Token decimal information for proper amount normalization
- **Wrapped token mappings**: Native wrapped token addresses for each supported chain to handle null address scenarios

## 3. Step-by-step calculation

### Component A: Core bridge transfers
- **Purpose**: Captures transfer volume through deBridge Messaging's main cross-chain bridge infrastructure
- **Logic**: Extracts `DeBridgeGate_Sent_event` logs from eight supported chains (Arbitrum, Avalanche, Base, BSC, Ethereum, Fantom, Optimism, and Polygon). Each event contains a `debridgeId` field that identifies the specific asset being transferred and an `amount` field indicating transfer volume. The system joins these events with the asset mapping dimension table to resolve the actual token address and destination chain for each deBridge Messaging asset ID. This mapping is necessary because deBridge Messaging uses internal asset identifiers rather than native token addresses in their transfer events.
- **Key fields**: Event includes `debridgeId` for asset identification, `amount` for transfer volume, block timestamp for daily aggregation, and transaction metadata for deduplication

### Component B: deBridge Liquidity Network (DLN) transfers  
- **Purpose**: Captures transfer volume through deBridge Messaging's Liquidity Network (deBridge Liquidity Network (DLN)) where users claim unlocked tokens
- **Logic**: Processes `DlnSource_ClaimedUnlock_event` logs from the same eight chains. These events track when users claim tokens that have been unlocked in the deBridge Liquidity Network (DLN) system. The logic includes special handling for native token transfers where the `giveTokenAddress` field contains null addresses (0x000...000). In these cases, the system replaces the null address with the appropriate wrapped native token address for each chain (such as WETH for Ethereum, WMATIC for Polygon, etc.). This ensures native token transfers are properly tracked and valued.
- **Key fields**: Events contain `giveTokenAddress` for token identification (with null address handling), `giveAmount` for transfer volume, and standard transaction metadata

### Final aggregation
- **Combining components**: Both transfer types are combined using a union operation, with each record timestamped to the day level. Core bridge transfers are classified under the "Interoperability" business line while deBridge Liquidity Network (DLN) transfers fall under "Bridging"
- **Currency conversion**: Transfer amounts are converted to USD using end-of-day token price feeds. The conversion process applies proper decimal correction based on each token's decimal configuration to ensure accurate volume calculations  
- **Time aggregation**: All transfers are aggregated to daily boundaries using timestamp truncation, with the system maintaining separate records for each chain and token combination
- **Final calculation**: The metric represents the sum of all USD-converted transfer volumes across both deBridge Messaging products for each day, with zero-filling applied for days with no transfer activity to maintain consistent time series data

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

Total value of assets moved across chains through a bridge.

deBridgeDBR

Transfer volume

Transfer volume

Competitive landscape

Chain breakdown