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 Active users (daily) Methodology

## 1. Overview

The deBridge Messaging daily active users (DAU) metric measures the number of unique users who perform cross-chain bridging transactions through the deBridge Messaging protocol each day. This metric answers the business question: "How many distinct users are actively using deBridge Messaging's interoperability services daily?" The calculation tracks users who initiate cross-chain transfers across deBridge Messaging's supported blockchain networks, providing a key indicator of protocol adoption and user engagement.

## 2. Data sources

- **deBridge Messaging protocol events**: Parsed `DeBridgeGate_Sent_event` logs from eight blockchain networks (Arbitrum, Avalanche, Base, BSC, Ethereum, Fantom, Optimism, Polygon)
- **Blockchain transaction data**: Block timestamps and transaction hashes from each supported network
- **Event parameters**: User addresses (`nativeSender` field) from bridge initiation events

## 3. Step-by-step calculation

### Component A: Multi-chain user data collection

- **Purpose**: Collect all user interactions with deBridge Messaging protocol across supported blockchain networks
- **Logic**: Extract data from `DeBridgeGate_Sent_event` logs across eight chains (Arbitrum, Avalanche, Base, BSC, Ethereum, Fantom, Optimism, Polygon). For each event, capture the `nativeSender` parameter which identifies the user initiating the cross-chain transfer. Include block timestamp for temporal analysis and transaction hash for transaction identification. Tag each record with the source chain and classify as 'interoperability' business segment with user type 'Sender'
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for uniqueness, `chain` for network identification, `nativeSender` as user address, `user_type` set to 'Sender'

### Component B: Daily user aggregation

- **Purpose**: Count distinct active users per day while maintaining chain-level granularity
- **Logic**: Truncate block timestamps to daily boundaries using day-level timestamp truncation. Group all user interactions by the truncated timestamp (daily grain) and chain. For each day-chain combination, count distinct user addresses to avoid double-counting users who perform multiple transactions on the same day. Preserve chain information to enable chain-specific DAU analysis
- **Key fields**: `timestamp` truncated to day level, `chain` for network identification, `user_dau` as the distinct user address count, `timestamp_grain` set to 'day'

### Final aggregation

- **Combining components**: The daily aggregation component directly processes the multi-chain user data collection, creating a streamlined flow from raw events to daily metrics
- **Time aggregation**: Daily boundaries are established through timestamp truncation to day level, ensuring consistent 24-hour periods across all time zones
- **Chain availability**: Apply chain availability filtering to ensure data quality and completeness across different blockchain networks, accounting for potential network downtime or data gaps
- **Final calculation**: The final DAU value represents the count of distinct user addresses who initiated cross-chain bridging transactions through deBridge Messaging protocol on each specific day and chain combination

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

Unique revenue-generating users over a fixed 24-hour window.

deBridgeDBR

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown