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 Average revenue per user (ARPU) Methodology

## 1. Overview

ARPU measures the average revenue generated per daily active user on the Allbridge cross-chain bridge protocol. The metric is calculated by dividing daily revenue by daily active users (DAU), providing insight into the protocol's monetization efficiency per user. This metric helps evaluate user value and protocol performance across different chains and time periods.

## 2. Data sources

- **Cross-chain bridge events**: Parsed `TokensSent` events from Allbridge `Bridge` and `Bridge2` contracts deployed on Ethereum, BSC, and Polygon networks
- **Bridge completion events**: Parsed `TokensReceived` events from Allbridge `Bridge2` contracts on Ethereum, BSC, and Polygon networks, used to capture transfers originating from Tron and Solana
- **End-of-day price feeds**: Daily closing prices for stablecoins and supported tokens to enable USD conversion
- **Token metadata**: Token decimal specifications for proper amount normalization
- **Chain mapping data**: Configuration mapping Allbridge chain IDs to blockchain network names

## 3. Step-by-step calculation

### Component A: Transfer volume collection

- **Purpose**: Aggregate all cross-chain bridge transfer volumes in USD
- **Logic**: Extract transfer data from `TokensSent` events across Ethereum, BSC, and Polygon, capturing destination chain ID, token address, and transfer amounts. For transfers to Tron and Solana (chains without decoded event access), extract data from `TokensReceived` events by parsing the origin chain ID from the message field and mapping to appropriate stablecoin addresses (BUSD on BSC, USDC on Ethereum/Polygon). Apply decimal correction by dividing amounts by 1000 (hardcoded 3-decimal precision). Convert all amounts to USD using end-of-day token price feeds, with Tron/Solana transfers priced using Ethereum USDC rates. Aggregate daily transfer volumes by chain and token.
- **Key fields**: `block_timestamp`, `destination_chain_id`, `token_address`, `transfer_amount`, `origin_chain_id` (parsed from message), `chain` (mapped destination chain name)

### Component B: Daily active user counting

- **Purpose**: Count distinct users performing bridge transfers each day
- **Logic**: Extract user addresses from the same bridge transfer events. For `TokensSent` events, use the `recipient` field directly. For `TokensReceived` events, parse the recipient address from the hex-encoded message field by extracting substring positions 27-40 and prefixing with "0x". Classify all users as "Trader" type within the "bridges" market sector and "mint_and_burn" business segment. Apply HyperLogLog (HLL) distinct counting algorithm to efficiently count unique users across multiple dimensional breakdowns: project-level aggregation, chain-level breakdowns, user-type breakdowns, and product-level breakdowns. Only include `TokensReceived` events from Tron and Solana origins (chain IDs 3 and 4) to avoid double-counting with `TokensSent` events.
- **Key fields**: `user_address` (recipient or parsed from message), `user_type`, `chain`, `block_timestamp`, `origin_chain_id`

### Component C: Revenue calculation

- **Purpose**: Calculate daily protocol revenue from bridge transfer fees
- **Logic**: Apply fee percentage rates to the USD-converted daily transfer volumes. Use time-based fee structure: 0.02% (0.0002) for transfers before January 30, 2023, and 0.06% (0.0006) for transfers on or after that date. Multiply each day's total transfer volume by the applicable fee percentage to calculate daily revenue. Aggregate revenue by day, chain, and product dimensions.
- **Key fields**: `transfer_volume` (USD), `timestamp`, `revenue` (calculated as volume × fee percentage)

### Final aggregation

- **Combining components**: Join daily revenue totals with daily active user counts by matching on timestamp and dimensional attributes (chain, product). Both components are aggregated to daily granularity and aligned on the same dimensional breakdowns (project-level, chain-level, user-type-level, product-level).
- **Currency conversion**: All transfer volumes are converted to USD using end-of-day token price feeds before revenue calculation, ensuring consistent currency denomination
- **Time aggregation**: Daily boundaries are applied using timestamp truncation to day level, with all events grouped by calendar day
- **Final calculation**: ARPU is calculated as daily revenue divided by daily active users (Revenue ÷ DAU) for each day and dimensional combination. Missing days are filled with zeros to ensure complete time series. The result provides average revenue per user in USD for each day, enabling tracking of user monetization trends across different chains and time periods.

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

Allbridge Core

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape