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 Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) measures the number of unique users who completed cross-chain bridge transactions through the Across protocol on any given day. This metric answers the question "How many distinct users actively used Across bridge services each day?" The calculation identifies unique recipient addresses from successful bridge completion events across all supported blockchain networks, providing insights into user engagement and protocol adoption.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Blockchain events**: Parsed Across protocol bridge completion events from Ethereum, Arbitrum, Base, BSC, Linea, Optimism, Polygon, Scroll, Worldchain, and zkSync Era networks
- **Bridge completion events**: `FilledRelay` and `FilledV3Relay` events from various Across SpokePool contract versions (V1, V2, V2.5) that represent successful cross-chain transfer completions
- **Transaction data**: Blockchain transaction records containing timestamps, transaction hashes, and event parameters for bridge operations
- **Chain availability data**: Information about operational periods for each blockchain network to ensure accurate counting only during active chain periods
- **Protocol metadata**: Fixed classifications for market sector (bridges), business segment (mint_and_burn), and user type (Trader) assignments

## 3. Step-by-step calculation

### Component A: User identification from bridge events
- **Purpose**: Extracts unique user addresses from completed bridge transactions across all supported chains
- **Logic**: Processes multiple types of Across protocol events including legacy V1 `BridgePoolProd_DepositRelayed_event` events and various V2/V2.5 SpokePool events. For each event type, extracts the recipient address field which represents the user who received funds on the destination chain. Different event versions use different parameter structures - older events use `recipient` field while newer V3 events use `relayExecutionInfo.updatedRecipient`. All users are classified as "Trader" type since they represent bridge transaction recipients.
- **Key fields**: `block_timestamp` for transaction timing, `transaction_hash` for deduplication, `recipient` or `updatedRecipient` for user identification, chain identifier for network attribution

### Component B: Daily user aggregation
- **Purpose**: Groups user activity by day and creates distinct user counts per chain
- **Logic**: Takes the extracted user addresses and truncates timestamps to daily boundaries using day-level granularity. Creates distinct combinations of date, chain, user_type, and user address to ensure each user is counted only once per day per chain. Applies chain availability filters to exclude time periods when specific blockchain networks were not operational or supported by the protocol.
- **Key fields**: `timestamp` truncated to day boundaries, `chain` for network identification, `user_type` for user classification, `user_address` for unique user identification

### Component C: HyperLogLog sketch creation
- **Purpose**: Converts daily user sets into HyperLogLog data structures for efficient approximate counting and aggregation
- **Logic**: Initializes HyperLogLog sketches with precision parameter 15 for each daily user set grouped by timestamp, chain, and user_type. This probabilistic data structure enables efficient storage and merging of large user sets while maintaining reasonable accuracy for cardinality estimation. Groups users by all dimensional attributes to prepare for subsequent aggregation steps.
- **Key fields**: `hll` sketch containing compressed user address information, dimensional grouping fields for aggregation control

### Component D: Dimensional breakdown generation
- **Purpose**: Creates multiple views of DAU data aggregated across different dimensional combinations
- **Logic**: Generates four separate dimensional breakdowns. First, project-level aggregation merges all HyperLogLog sketches across chains and user types to produce total protocol DAU. Second, chain-level breakdown maintains separate counts for each blockchain network. Third, user_type breakdown (though all users are currently "Trader" type) maintains this dimension. Fourth, product_id breakdown (currently null for all Across users) provides product-level granularity. Each breakdown uses HyperLogLog merge operations to combine sketches while maintaining user uniqueness within each dimensional group.
- **Key fields**: `dimensions` indicating breakdown type, `chain_id`, `product_id`, `user_type` for dimensional attributes, `user_dau` containing final counts

### Final aggregation
- **Combining components**: All dimensional breakdowns are combined using union operations to create a single result set with multiple granularity levels
- **Currency conversion**: Not applicable as DAU is a count metric
- **Time aggregation**: Daily boundaries established through timestamp truncation, with data partitioned by month for efficient querying
- **Final calculation**: HyperLogLog extract operations convert probabilistic sketches back to approximate distinct count integers, providing the final DAU values for each dimensional combination while maintaining uniqueness across the aggregation hierarchy

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

Unique revenue-generating users over a fixed 24-hour window.

AcrossACX

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown