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 fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average fee revenue generated per daily active user on the Allbridge protocol. This metric is calculated by dividing daily fee revenue by the number of daily active users. AFPU helps evaluate the monetization efficiency of the bridge protocol and user engagement quality. The calculation uses bridge transfer volume data to determine fees (applying time-based fee rates) and extracts user activity from the same bridge transactions.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Bridge event logs**: Parsed `TokensSent` events from Allbridge `Bridge` and `Bridge2` contracts deployed on Ethereum, BSC, and Polygon networks, containing transfer amounts, token addresses, recipient addresses, and destination chain identifiers
- **Cross-chain event logs**: Parsed `TokensReceived` events from Allbridge `Bridge2` contracts on Ethereum, BSC, and Polygon, used to capture transfer activity originating from Tron and Solana (chains without decoded event data)
- **Token pricing data**: End-of-day token price feeds for stablecoins including USDC on Ethereum and Polygon, and BUSD on BSC
- **Chain configuration**: Allbridge-specific mapping of chain IDs to chain names for cross-chain transfer routing

## 3. Step-by-step calculation

### Component A: Bridge transfer volume extraction

- **Purpose**: Capture all bridge transfer volumes across supported chains
- **Logic**: Extract `TokensSent` events from Allbridge contracts on Ethereum, BSC, and Polygon chains. Parse the `amount` field (transfer volume), `receiveToken` field (token address), `destinationChainId` field, and `recipient` field (user address). Apply decimal correction by dividing transfer amounts by 1000 since the events store amounts with only 3 decimal precision. Map destination chain IDs to chain names using the chain configuration mapping. For transfers to Tron or Solana (chains without decoded data), substitute token addresses with Ethereum USDC address for pricing purposes.
- **Key fields**: `amount` (raw transfer amount), `receiveToken` (token contract address), `destinationChainId` (numeric chain identifier), `recipient` (user wallet address)

### Component B: Cross-chain volume completion

- **Purpose**: Capture transfer volume from Tron and Solana chains that lack decoded event data
- **Logic**: Extract `TokensReceived` events from destination chains (Ethereum, BSC, Polygon) where the origin chain ID indicates Tron (ID=3) or Solana (ID=4). Parse the origin chain ID from the `message` field and the transfer amount. Map destination chain to appropriate stablecoin token address (BUSD for BSC, USDC for Ethereum and Polygon). This ensures complete volume coverage without double-counting transfers between EVM chains.
- **Key fields**: `message` (encoded origin chain information), `amount` (received transfer amount), `recipient` (destination user address)

### Component C: Fee calculation

- **Purpose**: Calculate protocol fee revenue from bridge transfers
- **Logic**: Apply time-based fee percentages to the USD-converted transfer volumes. Use 0.1% fee rate for transfers before January 30, 2023, and 0.3% fee rate for transfers after this date. Sum daily fees by chain and aggregate across all supported chains.
- **Key fields**: `transfer_volume` (USD-converted volume), `timestamp` (for fee rate determination)

### Component D: User activity tracking

- **Purpose**: Count daily active users across all bridge operations
- **Logic**: Extract user addresses from the `recipient` field of both `TokensSent` and `TokensReceived` events. For `TokensReceived` events, parse the recipient address from the hexadecimal message data. Deduplicate addresses per day using HyperLogLog aggregation to handle users making multiple transactions. Only include received transfers from Tron and Solana origins to avoid double-counting users already captured in sent transfers.
- **Key fields**: `recipient` (user wallet address), `message` (for parsing Tron/Solana user addresses)

### Final aggregation

- **Combining components**: Sum daily fee revenue and count daily unique users for each chain and date combination
- **Currency conversion**: Convert stablecoin transfer amounts to USD using end-of-day price feeds specific to each destination chain's token (USDC prices for most chains, BUSD prices for BSC transfers)
- **Time aggregation**: Group all metrics by day using timestamp truncation to daily boundaries
- **Final calculation**: Divide daily fee revenue by daily active user count to produce the average fees per user metric. Apply zero-filling strategy for days with no activity to maintain continuous time series data.

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

Allbridge Core

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape