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 Transfer volume Methodology

## 1. Overview

Transfer volume measures the total USD value of assets transferred through the Across protocol's cross-chain bridge on a daily basis. This metric captures bridge deposit activity across all versions of the Across protocol (v1, v2, v2.5, and v3) and multiple blockchain networks. The calculation aggregates raw transfer amounts from blockchain events, converts them to USD using end-of-day price feeds, and presents daily totals. This metric answers how much value flows through the Across bridge infrastructure each day.

## 2. Data sources

The calculation uses several types of blockchain and external data:

- **Across protocol events**: Parsed `FundsDeposited` events from Across v2 spoke pool contracts on Ethereum, Polygon, Arbitrum, Optimism, Base, and zkSync Era networks
- **Across v2.5 protocol events**: Parsed `FundsDeposited` events from Across v2.5 spoke pool contracts on Ethereum, Polygon, Arbitrum, Optimism, Base, zkSync Era, BSC, Linea, Scroll, and Worldchain networks
- **Across v3 protocol events**: Parsed `V3FundsDeposited` events from Across v2.5 proxy contracts (used by v3) across the same 10 chains as v2.5
- **Across v1 protocol events**: Parsed `DepositRelayed` events from Across v1 bridge pool contracts on Ethereum only
- **Token metadata**: Token decimals, symbols, and addresses for proper amount calculations
- **End-of-day price feeds**: Daily token price data for USD conversion
- **Trading pool metadata**: Mapping between v1 bridge pool contract addresses and their associated tokens

## 3. Step-by-step calculation

### Component A: V1 bridge transfers
- **Purpose**: Extract transfer data from the original Across v1 protocol on Ethereum
- **Logic**: Parse `DepositRelayed` events from v1 bridge pool contracts and join with trading pool metadata to identify the associated token. Extract the deposit `amount` from the event data along with LP fee and relayer fee percentages. Calculate fee amounts by multiplying percentages with transfer amounts. The component focuses only on the raw `transfer_amount` for volume calculation
- **Key fields**: `block_timestamp` for timing, `amount` as the raw transfer volume, `address` as the bridge pool contract, and derived `token_address` from pool metadata

### Component B: V2 bridge transfers  
- **Purpose**: Extract transfer data from Across v2 spoke pool contracts across multiple chains
- **Logic**: Parse `FundsDeposited` events from both regular and V2 spoke pool contracts on Ethereum, Polygon, Arbitrum, Optimism, Base, and zkSync Era. Extract the `originToken` address and `amount` fields directly from event parameters. Each event represents a user deposit into a spoke pool for cross-chain bridging
- **Key fields**: `block_timestamp` for timing, `originToken` as token address, `amount` as transfer volume, and `address` as the spoke pool contract

### Component C: V2.5 bridge transfers
- **Purpose**: Extract transfer data from upgraded Across v2.5 spoke pool contracts with expanded chain support
- **Logic**: Parse `FundsDeposited` events from V2.5 spoke pool contracts across 10 chains including newer networks like BSC, Linea, Scroll, and Worldchain. Extract `inputToken` and `inputAmount` from events, applying address formatting to convert token addresses using substring operations to ensure proper hex format
- **Key fields**: `block_timestamp` for timing, formatted `inputToken` as token address, `inputAmount` as transfer volume

### Component D: V3 bridge transfers
- **Purpose**: Extract transfer data from Across v3 protocol using V3-specific events
- **Logic**: Parse `V3FundsDeposited` events emitted through v2.5 proxy contracts but representing v3 protocol logic. Extract `inputToken` and `inputAmount` fields, applying the same address formatting as v2.5. These events represent the latest version of the protocol with enhanced functionality
- **Key fields**: `block_timestamp` for timing, formatted `inputToken` as token address, `inputAmount` as transfer volume

### Final aggregation
- **Combining components**: Union all four components using identical schema with standardized field names. Each record includes daily timestamp, chain identifier, market sector as 'bridges', business segment as 'mint_and_burn', and the raw transfer amount
- **Currency conversion**: Apply USD conversion using end-of-day price feeds matched by token address and date. Correct for token decimals by dividing raw amounts by the appropriate power of 10 based on token metadata
- **Time aggregation**: Truncate all timestamps to daily boundaries and group by day, chain, and token. Sum USD-converted transfer amounts within each group
- **Final calculation**: The final transfer volume equals the sum of all USD-converted bridge deposits for each day, representing the total value flowing through the Across protocol bridge infrastructure

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

Total value of assets moved across chains through a bridge.

AcrossACX

Transfer volume

Transfer volume

Competitive landscape

Chain breakdown