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

## 1. Overview

The Allbridge expenses metric measures the operational costs and token incentive payments made by the Allbridge protocol. This metric represents expenditures that reduce the protocol's net revenue and includes items like token rewards, grants, or other operational costs. For Allbridge, expenses are currently set to zero as the protocol does not distribute token incentives or incur other tracked operational expenses. The calculation framework processes the underlying bridge transfer data to establish the foundation for expense calculations, even though the final expense values are zero.

## 2. Data sources

The methodology relies on the following raw data sources:

- **Blockchain events**: Parsed `Bridge_TokensSent_event` and `Bridge2_TokensSent_event` logs from Ethereum, BSC, and Polygon networks, plus `Bridge2_TokensReceived_event` logs from the same chains. These events capture cross-chain bridge transfers processed by Allbridge contracts.
- **Transaction data**: Blockchain transaction logs containing bridge transfer details including destination chains, transfer amounts, and token addresses
- **External data**: End-of-day token price feeds for USD conversion of transfer volumes, and token metadata containing decimal precision information for amount calculations
- **Chain metadata**: Allbridge-specific chain ID mappings covering Ethereum (1), BSC (2), Tron (3), Solana (4), and Polygon (5) networks

## 3. Step-by-step calculation

### Component A: Bridge transfer extraction
- **Purpose**: Extract and process raw bridge transfer events from supported blockchain networks
- **Logic**: Parse `Bridge_TokensSent_event` and `Bridge2_TokensSent_event` logs from Ethereum, BSC, and Polygon contracts. Extract key transfer details including block timestamps, transaction hashes, destination chain IDs, token addresses (converted from hex format), and transfer amounts. For received transfers, process `Bridge2_TokensReceived_event` logs to capture transfers originating from Tron and Solana where direct event data isn't available. Apply chain-specific token address mappings, using BUSD for BSC destinations, USDC for Ethereum destinations, and USDC for Polygon destinations.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `destinationChainId` and `originChainId` for cross-chain routing, `receiveToken` and converted `token_address` for asset identification, and `amount` for transfer values

### Component B: Transfer volume aggregation  
- **Purpose**: Calculate daily USD transfer volumes across all supported chains and tokens
- **Logic**: Group processed transfer events by day, chain, and token address. Sum transfer amounts after correcting for token decimal places (transfers have 3-decimal precision requiring division by 1000). For cross-chain transfers to Tron or Solana, use Ethereum USDC pricing since direct price feeds aren't available for those networks. Convert all transfer amounts to USD using end-of-day price feeds matched by date, chain, and token address. Apply the transfers_received logic to avoid double-counting by only including received transfers from Tron and Solana origins.
- **Key fields**: Daily aggregated `transfer_volume` in USD, `chain_id` for network identification, and `token_address` for asset tracking

### Component C: Fee calculation framework
- **Purpose**: Calculate theoretical fees that could be charged on transfer volumes
- **Logic**: Apply percentage-based fees to USD transfer volumes using time-dependent rates. Use 0.1% fee rate for transfers before January 30, 2023, and 0.3% rate for transfers afterward. This creates a fee calculation framework even though Allbridge doesn't currently charge fees. Aggregate fees by day, chain, and maintain the same dimensional structure as transfer volumes.
- **Key fields**: Calculated `fees` values based on volume multiplication with fee percentages, maintaining temporal and chain dimensions

### Component D: Token incentive determination
- **Purpose**: Define token incentive payments made by the protocol  
- **Logic**: Set token incentives to zero across all time periods, chains, and products. This reflects Allbridge's current policy of not distributing token rewards or operational incentives. Maintain the same dimensional structure as the fee calculation to ensure consistency across the metric framework.
- **Key fields**: `token_incentives` set to 0 for all records, with preserved `timestamp`, `chain_id`, and `product_id` dimensions

### Final aggregation
- **Combining components**: Take token incentive values directly as expense values, since expenses represent the same concept of protocol operational costs and token distributions
- **Currency conversion**: Already handled in the underlying transfer volume calculation using end-of-day USD price feeds
- **Time aggregation**: Maintain daily grain with proper timestamp boundaries and zero-filling for missing dates
- **Final calculation**: Expenses equal token incentives, which are set to zero for all time periods and chains. This results in zero expenses across the entire Allbridge dataset, reflecting the protocol's current operational model without token distributions or other tracked expenses.

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

Total project operating and incentive expenses.

Allbridge Core

Expenses

Expenses

Competitive landscape

Chain breakdown