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 (monthly) Methodology

## 1. Overview

The deBridge Messaging Monthly Active Users (MAU) metric measures the number of unique users who have initiated cross-chain transactions through the deBridge Messaging protocol within rolling 30-day periods. This metric answers the business question: "How many distinct users are actively using deBridge Messaging for interoperability services each month?" The calculation uses HyperLogLog approximation algorithms to efficiently compute unique user counts across multiple dimensions while handling the large scale of blockchain transaction data.

## 2. Data sources

The MAU calculation relies on the following raw data sources:
- **Blockchain events**: Parsed `Sent` events from DeBridgeGate smart contracts deployed across eight blockchain networks: Ethereum, Arbitrum, Avalanche, Base, BSC (Binance Smart Chain), Fantom, Optimism, and Polygon
- **Event parameters**: The `nativeSender` parameter from each `Sent` event, which identifies the wallet address that initiated the cross-chain transaction
- **Transaction metadata**: Block timestamps and transaction hashes from each blockchain to establish timing and uniqueness of user activities
- **Chain availability data**: Blockchain network availability status used for data quality filtering

## 3. Step-by-step calculation

### Component A: User activity extraction
- **Purpose**: Extract and standardize user activity data from cross-chain transaction events across all supported blockchain networks
- **Logic**: The system processes parsed `Sent` events from DeBridgeGate contracts on eight different blockchains. For each event, it extracts the `nativeSender` parameter which represents the wallet address initiating the cross-chain transaction. All extracted user addresses are classified as 'Sender' type users, categorized under the 'interoperability' market sector and business segment. The system standardizes the data structure across all chains while preserving the original chain identifier and block timestamp for each transaction.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for uniqueness, `chain` identifier, `user_address` from `nativeSender` parameter, and `user_type` set to 'Sender'

### Component B: Daily active users aggregation  
- **Purpose**: Calculate daily unique active users by aggregating transaction activity to daily granularity
- **Logic**: The system processes the standardized user activity data by truncating block timestamps to daily boundaries and identifying distinct user addresses for each day. This aggregation is performed across multiple dimensions including chain, user type, and product ID (which remains null for deBridge Messaging). Chain availability filtering is applied to ensure only data from operational blockchain networks is included in the calculations.
- **Key fields**: `timestamp` truncated to day level, `chain` identifier, `user_type`, `product_id`, and distinct `user_address` representing daily active users

### Component C: HyperLogLog conversion and window creation
- **Purpose**: Convert daily active user data into HyperLogLog sketches and create rolling 30-day calculation windows
- **Logic**: The system converts the daily active user data into HyperLogLog sketches using a precision parameter of 15, enabling memory-efficient approximate counting of unique users. A complete datespine is generated covering all days from the earliest available data to the current date to ensure no timestamps are skipped. For each day in the datespine, the system creates a 30-day rolling window by generating timestamps for the current day plus the previous 29 days, then joins this window with the HLL-converted daily user data.
- **Key fields**: HyperLogLog sketches containing user data (`hll`), `timestamp` for the current day, `joinday` for the 29-day lookback period, and dimensional attributes (`chain_id`, `user_type`, `product_id`)

### Component D: Dimensional MAU breakdowns
- **Purpose**: Calculate monthly active users across different dimensional breakdowns for analytical flexibility
- **Logic**: The system creates four distinct dimensional views of the MAU data. The project-level breakdown aggregates all users across all dimensions. The chain-level breakdown groups users by individual blockchain networks. The user-type breakdown segments users by their classification (currently all 'Sender' type). The product-level breakdown groups by product ID (currently null for deBridge Messaging). For each breakdown, HyperLogLog sketches within the 30-day windows are merged using the `hll_count.merge_partial` function, then extracted to final unique user counts using `hll_count.extract`.
- **Key fields**: `user_mau` representing the final monthly active user count, `dimensions` indicating the breakdown type, and relevant dimensional attributes (`chain_id`, `user_type`, `product_id`)

### Final aggregation
- **Combining components**: The four dimensional breakdowns are combined using UNION ALL operations to create a comprehensive dataset containing MAU calculations across all dimensional perspectives
- **Currency conversion**: No currency conversion is required as this metric counts users rather than monetary values
- **Time aggregation**: The metric uses rolling 30-day windows calculated daily, providing a smooth trending view of monthly active users rather than discrete monthly boundaries
- **Final calculation**: The final MAU value is extracted from merged HyperLogLog sketches representing unique users who initiated at least one cross-chain transaction within the rolling 30-day period, providing an approximate but highly accurate count of monthly active users across the deBridge Messaging protocol

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

Unique revenue-generating users over a rolling 30-day window.

deBridgeDBR

Active users (monthly)

Active users (monthly)

Competitive landscape

Chain breakdown