Allbridge Core allows users to send stablecoins from one chain to another almost immediately by using native liquidity pools deployed across 5 EVM and non-EVM blockchains. Liquidity providers receive the majority of transfer fees paid by users (supply-side fees).

Allbridge Core is a cross-chain stablecoin bridge. Allbridge Core was co-founded by Yuriy Savchenko and Andriy Velykyy, and was launched in September 2022.

The Allbridge team own and govern the protocol. They currently take a cut of the transfer fees paid by the users (revenue). Allbridge Core’s investors include Race Capital and others.

github

twitter

discord

website

Bridges

Allbridge Core

# Allbridge Core Active users (daily) Methodology

## 1. Overview

Daily active users (DAU) for Allbridge measures the number of unique user addresses that interact with Allbridge's cross-chain bridge protocol on any given day. This metric captures both users who send tokens to other chains and users who receive tokens from non-EVM chains (Solana and Tron), providing a comprehensive view of bridge usage while avoiding double counting.

## 2. Data sources

The calculation relies on several key blockchain data sources:
- **Allbridge bridge events**: Parsed `TokensSent` events from Allbridge v1 and v2 bridge contracts on BSC, Ethereum, and Polygon chains
- **Cross-chain receive events**: Parsed `TokensReceived` events from Allbridge bridge contracts on BSC, Ethereum, and Polygon
- **Transaction metadata**: Blockchain transaction timestamps, transaction hashes, and block data from supported chains
- **Cross-chain identifiers**: Origin chain ID data embedded in bridge messages to identify transaction sources
- **User address data**: Recipient and sender addresses extracted from bridge event parameters

## 3. Step-by-step calculation

### Component A: Token sending users
- **Purpose**: Identifies users who initiate bridge transactions by sending tokens to other chains
- **Logic**: Extracts user addresses from `TokensSent` events across Allbridge v1 and v2 bridge contracts on BSC, Ethereum, and Polygon. The `recipient` parameter from these events contains the destination address for the bridged tokens. All users are classified as 'Trader' type and associated with the 'bridges' market sector and 'mint_and_burn' business segment.
- **Key fields**: Block timestamps for timing, transaction hashes for uniqueness, `recipient` addresses as user identifiers, and chain identifiers for source chain tracking

### Component B: Token receiving users  
- **Purpose**: Captures users who receive tokens from non-EVM chains to avoid missing cross-chain activity
- **Logic**: Processes `TokensReceived` events from bridge contracts, but applies filtering based on origin chain ID to prevent double counting. Only includes transactions where the origin chain ID is 3 (Tron) or 4 (Solana), ensuring that users receiving tokens from these non-EVM chains are counted without duplicating users who sent tokens on the same EVM chain. The `recipient` address is extracted and formatted by converting hex data to proper address format.
- **Key fields**: Block timestamps, transaction hashes, formatted `recipient` addresses, and `origin_chain_id` extracted from message data for filtering

### Final aggregation
- **Combining components**: Both token sending and token receiving user sets are combined using union operations, creating a comprehensive list of all bridge users while the origin chain ID filtering prevents double counting
- **Time aggregation**: Block timestamps are truncated to daily boundaries using day-level granularity, grouping all user activity within each calendar day
- **User deduplication**: Distinct user addresses are selected within each day, ensuring that users who perform multiple bridge transactions on the same day are only counted once
- **Final calculation**: The daily active user count is the number of unique user addresses that appear in either token sending or qualified token receiving events for each day, with chain availability filtering applied to ensure data completeness

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

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

Allbridge Core

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown