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 Fees Methodology

## 1. Overview

Allbridge fees represent the total fees earned by the Allbridge protocol from cross-chain bridge transfers. The metric is calculated by applying percentage-based fees to the total transfer volume processed through Allbridge's bridge infrastructure. This metric helps measure the protocol's fee-generating activity across multiple blockchain networks including Ethereum, BSC, Polygon, Tron, and Solana.

## 2. Data sources

- **Ethereum events**: Parsed `TokensSent` and `TokensReceived` events from Allbridge bridge contracts
- **BSC events**: Parsed `TokensSent` and `TokensReceived` events from Allbridge bridge contracts  
- **Polygon events**: Parsed `TokensSent` and `TokensReceived` events from Allbridge bridge contracts
- **Chain mapping data**: Allbridge-specific chain ID mappings for cross-chain transfer routing
- **Token metadata**: Token contract addresses and decimal specifications for accurate amount calculations
- **External price data**: End-of-day token price feeds for USD conversion of stablecoin volumes

## 3. Step-by-step calculation

### Component A: Bridge transfer extraction
- **Purpose**: Extract and standardize bridge transfer data from multiple blockchain networks
- **Logic**: The system processes both outbound transfers using `TokensSent` events and inbound transfers using `TokensReceived` events from Allbridge bridge contracts. For outbound transfers, the system extracts the destination chain ID, token address, and transfer amount. For inbound transfers, it extracts the origin chain ID from encoded message data and processes the received amount. Token addresses are standardized using hardcoded mappings for USDC and BUSD across different chains.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for uniqueness, `destinationChainId` and `originChainId` for routing, `amount` for transfer size, `receiveToken` and token addresses for asset identification

### Component B: Cross-chain deduplication and routing  
- **Purpose**: Prevent double-counting of transfers while ensuring complete coverage across all supported chains
- **Logic**: The system applies a sophisticated deduplication strategy by processing sent transfers from Ethereum, BSC, and Polygon, while only processing received transfers from Tron and Solana (chain IDs 3 and 4). This approach captures transfer activity from chains where direct event access may be limited while avoiding duplicate counting of the same bridge transaction. Chain mapping converts numeric chain IDs to chain names for consistent processing.
- **Key fields**: `origin_chain` and `destination_chain` for transfer routing, `chain` for data source identification, `chain_id` for mapping lookups

### Component C: Volume calculation and standardization
- **Purpose**: Calculate daily transfer volumes with proper decimal handling and USD conversion
- **Logic**: Transfer amounts undergo decimal correction by dividing by 1000 to account for the 3-decimal precision used in the contract events. The system then aggregates transfer amounts by day, chain, and token address. For chains like Tron and Solana that use proxy pricing, the system maps their tokens to Ethereum USDC for price lookup. Stablecoin volumes are converted to USD using end-of-day price feeds.
- **Key fields**: `transfer_amount` after decimal correction, `token_address` for price lookup, `timestamp` truncated to daily boundaries

### Component D: Fee percentage application
- **Purpose**: Apply time-based fee rates to calculate protocol fees from transfer volumes
- **Logic**: The system applies different fee percentages based on the transfer date. For transfers before January 30, 2023, a fee rate of 0.1% (0.001) is applied. For transfers on or after January 30, 2023, a higher fee rate of 0.3% (0.003) is applied. This reflects a protocol upgrade that increased fee rates.
- **Key fields**: `timestamp` for date comparison, `transfer_volume` for fee calculation base, `fees` as the calculated result

### Final aggregation
- **Combining components**: Transfer volumes from all chains and time periods are combined into a single dataset, with fees calculated by multiplying each volume amount by the applicable time-based percentage rate
- **Currency conversion**: All stablecoin transfer volumes are converted to USD using end-of-day price feeds, with special handling for Tron and Solana tokens that use Ethereum USDC pricing as a proxy
- **Time aggregation**: All transfer data is aggregated to daily boundaries using timestamp truncation to day level, ensuring consistent time-based reporting
- **Final calculation**: Fees equal transfer volume multiplied by the applicable fee percentage (0.1% before January 30, 2023, and 0.3% after that date), with all amounts expressed in USD after price conversion and decimal correction

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

Total value users pay to use a protocol (gross fees, user-paid fees).

Allbridge Core

Fees

Fees

Competitive landscape

Chain breakdown