Axelar Network node operators validate cross-chain transactions. They currently take a cut of transfer fees (supply-side fees).

Axelar Network is an interoperability protocol that allows for decentralized transfers of data and assets between blockchains. Axelar Network was founded by Sergey Gorbunov and Georgios Vlachos, and was launched in 2022. This dashboard currently only includes data for the following chains: Arbitrum, Avalanche, Base, BNB Chain, Celo, Ethereum, Fantom, Optimism, and Polygon.

AXL tokenholders own and govern the protocol. They currently take a cut of transfer fees paid by transfer senders (revenue). Axelar Network’s investors include Polychain Capital, Dragonfly Capital, North Island Ventures, etc.

github

twitter

discord

etherscan

website

Interoperability

Axelar Network

# Axelar Network Active users (weekly) Methodology

## 1. Overview

The Weekly Active Users (WAU) metric measures the number of unique users who interacted with Axelar's cross-chain infrastructure within any 7-day rolling window. This metric captures users engaging with Axelar's General Message Passing (GMP) functionality and cross-chain token transfers across multiple supported blockchain networks. The calculation uses a rolling 7-day window approach with HyperLogLog aggregation for efficient distinct user counting.

## 2. Data sources

- **Axelar Gateway events**: Parsed blockchain events from Axelar Gateway contracts deployed across Ethereum, Arbitrum, Avalanche, Base, BSC, Celo, Fantom, Optimism, and Polygon, including `ContractCall`, `ContractCallWithToken`, `Executed`, and `TokenSent` events
- **Token transfer events**: Blockchain token transfer logs that accompany Axelar Gateway interactions
- **Transaction records**: Blockchain transaction data containing user addresses and transaction metadata
- **Token metadata**: Token symbol and decimal information for transfer amount calculations
- **Chain mapping data**: Configuration data for cross-chain deduplication logic

## 3. Step-by-step calculation

### Component A: GMP transaction users
- **Purpose**: Identifies users initiating General Message Passing transactions through Axelar Gateway contracts
- **Logic**: Extracts users from `ContractCallWithToken` and `ContractCall` events across all supported chains. For token-based calls, captures amount and symbol directly from the event. For non-token calls, joins with token transfer logs (using log_index + 1 relationship) and token metadata to determine transfer amounts and symbols. Identifies users as transaction originators through the `from_address` field from transaction records.
- **Key fields**: `block_timestamp`, `user_address`, `chain`, `product_id` ('axelarnetworkv1'), `user_type` ('Sender')

### Component B: Destination chain transfer users  
- **Purpose**: Captures users receiving cross-chain transfers on destination chains
- **Logic**: Identifies users from `Gateway_Executed` events that represent successful cross-chain transfer completions. Joins executed events with token transfer logs (using log_index + 1 relationship) and transaction records to extract user addresses and transfer amounts. This captures both GMP transfers and token transfers executed on destination chains.
- **Key fields**: `block_timestamp`, `user_address`, `chain`, `token_address`, `amount`

### Component C: Source chain transfer users
- **Purpose**: Identifies users initiating cross-chain transfers from source chains
- **Logic**: Extracts users from `Gateway_TokenSent` events representing cross-chain transfer initiations. Filters out destinations that are EVM chains tracked by Token Terminal (using chain mapping data) to prevent double-counting with destination chain events. This ensures coverage of transfers to non-EVM chains or untracked destinations while avoiding duplication.
- **Key fields**: `block_timestamp`, `user_address`, `chain`, `destination_chain`, `amount`

### Component D: Daily active user aggregation
- **Purpose**: Combines all user interaction types into daily active user counts
- **Logic**: Unions users from GMP transactions, destination transfers, and source transfers. Truncates all timestamps to daily granularity and ensures distinct users per day across all interaction types. Classifies all users as 'Sender' type under the 'interoperability' business segment with 'axelarnetworkv1' as the product identifier.
- **Key fields**: `timestamp` (daily), `chain`, `user_type`, `product_id`, `user_dau`

### Component E: Seven-day rolling window creation
- **Purpose**: Establishes 7-day rolling windows for WAU calculation
- **Logic**: Creates a datespine covering all dates from the earliest DAU record to present. For each date in the datespine, generates a 7-day lookback window (current date plus 6 previous days) using joinday logic. Joins this window with daily user data to capture all users active within each 7-day period.
- **Key fields**: `timestamp`, `joinday`, daily HLL user sets

### Final aggregation
- **Combining components**: Uses HyperLogLog data structure to efficiently merge and count distinct users across the 7-day rolling windows, handling overlapping users between days within the window
- **Currency conversion**: Not applicable for user counting metrics
- **Time aggregation**: Calculates rolling 7-day windows for each date, where each day's WAU represents unique users active in that day plus the previous 6 days
- **Final calculation**: Applies HyperLogLog merge and extract functions to count distinct users within each 7-day window, creates four dimensional breakdowns (project-level, chain-level, user type-level, and product-level), and formats results with standardized schema including zero-filling for missing dates

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

Unique revenue-generating users over a rolling 7-day window.

Axelar NetworkAXL

Archived

Active users (weekly)

Active users (weekly)

Competitive landscape

Chain breakdown