Across allows users to send tokens from one chain to another almost immediately without having to wait for the rollup’s challenge period. Liquidity providers provide liquidity and relayers handle the fills and in return they charge a transfer fee (supply-side fees).

Across is a cross-chain token bridge for L2s and rollups. Across was founded by Hart Lambur and launched in 2021.

ACX tokenholders own and govern the protocol. They currently don’t take a cut of the total transfer fees paid by the users (revenue). Across’ investors include Hack VC, Placeholder and Blockchain Capital.

governance

github

twitter

discord

etherscan

website

Bridges

Across

# Across Revenue Methodology

## 1. Overview

The Across protocol revenue metric measures the fees retained by the protocol as revenue. However, Across operates as a fee-sharing bridge protocol where all collected fees are distributed to liquidity providers and relayers rather than retained by the protocol. Therefore, the revenue metric is intentionally set to zero while maintaining the underlying fee calculation infrastructure for transparency and consistency with other protocol metrics.

## 2. Data sources

The methodology relies on several key data sources:

- **Cross-chain bridge events**: Parsed `FilledRelay`, `FilledV3Relay`, and `DepositRelayed` events from Across protocol contracts across Ethereum, Arbitrum, Optimism, Base, Polygon, zkSync Era, BSC, Linea, Scroll, Worldchain, and Gnosis chains
- **Token mapping events**: Parsed `HubPool_SetPoolRebalanceRoute` events from Ethereum that establish cross-chain token address relationships
- **End-of-day price feeds**: Daily token price data for USD conversion
- **Token metadata**: Token decimals, symbols, and chain-specific information for proper unit conversion
- **Chain configuration data**: Mapping of chain IDs to chain names for multi-chain data normalization

## 3. Step-by-step calculation

### Component A: Protocol version data collection
- **Purpose**: Gather bridge transaction data across all Across protocol versions (V1, V2, V2.5, V3)
- **Logic**: Extract filled relay events and deposit events from version-specific smart contracts across all supported chains. V1 data comes from Ethereum `BridgePoolProd_DepositRelayed` events with LP fee and relayer fee percentages. V2 data comes from `FilledRelay` events across multiple chains with realized LP fees and applied relayer fees. V2.5 uses updated contract versions with similar event structures. V3 uses `FilledV3Relay` events through V2.5 contracts with enhanced relay execution information. Filter out invalid transactions and denied relayers based on hardcoded exclusion lists.
- **Key fields**: `block_timestamp`, `transaction_hash`, `token_address`, `transfer_amount`, `lp_fee_percentage`, `relayer_fee_percentage`, `input_amount`, `output_amount`, `origin_chain`, `destination_chain`

### Component B: Cross-chain token normalization  
- **Purpose**: Normalize token addresses across different chains to enable consistent pricing and calculation
- **Logic**: Use token mapping data from `HubPool_SetPoolRebalanceRoute` events to convert chain-specific token addresses to their L1 Ethereum equivalents. This ensures price consistency when the same token exists on multiple chains with different addresses. Join relay data with token mappings based on origin chain and destination chain to identify the L1 token address for both input and output tokens.
- **Key fields**: `chain_token_address`, `l1_address`, `chain_id`, `destination_chain_id`

### Component C: Fee calculation by version
- **Purpose**: Calculate fees using version-specific methodologies
- **Logic**: For V1 and V2, calculate fees by applying percentage rates to transfer amounts. Multiply LP fee percentage and relayer fee percentage by the transfer amount to get absolute fee amounts, then sum them. For V2.5 and V3, calculate fees as the USD difference between input amounts and output amounts after decimal correction and price conversion. Apply token decimal correction using metadata to convert raw blockchain amounts to proper token units. Convert all amounts to USD using end-of-day price feeds matched by timestamp, token address, and chain.
- **Key fields**: `lp_fee_amount`, `relayer_fee_amount`, `fees`, `input_amount_usd`, `output_amount_usd`

### Component D: Data quality and filtering
- **Purpose**: Remove invalid or spam transactions that could skew results
- **Logic**: Exclude specific transaction hashes known to cause data spikes or errors. Filter out fills from denied relayers after specific dates when they were identified as problematic. Apply chain availability filtering to ensure only supported chain data is included in final results.
- **Key fields**: `transaction_hash`, `relayer`, `block_timestamp`, `chain_id`

### Final aggregation
- **Combining components**: Combine fee data from all protocol versions using union operations, standardizing field names and adding consistent business line categorizations. All bridge activity is classified under the "Bridging" business line with "bridges" market sector and "mint_and_burn" business segment identifiers.
- **Currency conversion**: Convert all fee amounts to USD using end-of-day price feeds, matching by date, token L1 address, and chain. Use L1 token addresses for price lookups to avoid cross-chain price discrepancies.
- **Time aggregation**: Aggregate all fee data to daily boundaries using `timestamp_trunc` to the day level. Group by timestamp, chain, and business categorizations.
- **Final calculation**: Despite calculating comprehensive fee data, the final revenue metric is set to zero for all records because Across protocol does not retain any fees as revenue - all fees are distributed to liquidity providers and relayers. The zero revenue values are applied while maintaining proper schema structure through the `finalize_metric_revenue` macro.

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

AcrossACX

Revenue

Revenue

Competitive landscape

Chain breakdown