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 Average revenue per user (ARPU) Methodology

## 1. Overview

ARPU measures the average revenue generated per daily active user on the Across protocol bridge. The metric is calculated by dividing daily revenue by the number of daily active users. In Across protocol's current methodology, revenue is set to zero for all periods, resulting in an ARPU of $0. This indicates that the protocol treats bridge fees as operational costs rather than revenue in this specific calculation.

## 2. Data sources

- **Cross-chain bridge events**: Parsed `FilledRelay` events from Ethereum, Arbitrum, Base, Optimism, Polygon, BSC, Gnosis, Linea, Scroll, Worldchain, and zkSync Era across protocol versions v2, v2.5, and v3
- **Legacy bridge events**: Parsed `DepositRelayed` events from Ethereum for protocol version v1  
- **End-of-day price feeds**: Token price data in USD for fee calculations (though not used in final revenue)
- **Token metadata**: Token decimals and cross-chain address mappings
- **Chain configuration**: Chain ID mappings and supported network identifiers

## 3. Step-by-step calculation

### Component A: Daily active users calculation
- **Purpose**: Count distinct users who received cross-chain transfers each day
- **Logic**: Extract recipient addresses from all bridge completion events across supported chains and protocol versions. For v1 events, use the `l1Recipient` field from `DepositRelayed` events. For v2/v2.5/v3 events, use the `recipient` field from `FilledRelay` events, with v3 events using the `updatedRecipient` field when available. Group by day and count distinct user addresses using HyperLogLog aggregation for efficient computation across multiple dimensional breakdowns
- **Key fields**: `recipient`, `l1Recipient`, `updatedRecipient` addresses from bridge events, `block_timestamp` for daily grouping

### Component B: Revenue calculation  
- **Purpose**: Calculate daily revenue generated by the protocol
- **Logic**: The revenue component explicitly sets all revenue values to zero for all days and chains. While the underlying fee calculation methodology exists (combining LP fees and relayer fees from bridge events, converting to USD using end-of-day price feeds), the final revenue metric treats these fees as costs rather than protocol revenue
- **Key fields**: Revenue is hardcoded to 0, with dimensional structure pulled from the fees calculation

### Component C: Bridge fee methodology (for context)
- **Purpose**: Calculate actual fees paid by users (not used in revenue)
- **Logic**: For v1/v2 protocols, extract explicit LP fee and relayer fee percentages from events and multiply by transfer amounts. For v2.5/v3 protocols, calculate fees as the USD difference between input amounts and output amounts after correcting for token decimals and converting to USD using end-of-day price feeds. Filter out invalid transactions and denied relayers to prevent data anomalies
- **Key fields**: `realizedLpFeePct`, `relayerFeePct`, `inputAmount`, `outputAmount`, token addresses

### Final aggregation
- **Combining components**: ARPU is calculated by dividing daily revenue by daily active users for each chain and day
- **Currency conversion**: All values are in USD, with revenue set to zero
- **Time aggregation**: Data is aggregated at daily boundaries using transaction timestamps truncated to day level
- **Final calculation**: Since revenue equals zero for all periods, ARPU equals zero divided by daily active users, resulting in $0 ARPU for all days and chains. Missing days are filled with zeros rather than null values.

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

AcrossACX

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape