LayerZero uses a decentralized network of Validator Nodes to facilitate secure and fast communication between different blockchains.

LayerZero allows users to send and receive messages between different blockchains, and to bridge tokens between different blockchains.

LayerZero is a cross-chain interoperability protocol that enables secure and fast communication between different blockchains.

twitter

etherscan

website

Interoperability

LayerZero

# LayerZero Active users (weekly) Methodology

## 1. Overview

Active users (weekly) is measured as the number of unique addresses that make a revenue-generating transaction with LayerZero over a 7-day rolling window. The protocol is designed as an omnichain interoperability protocol that enables cross-chain communication and asset transfers. Unique wallet addresses are captured across LayerZero V1, LayerZero V2, and Stargate. Unique addresses that either send or receive cross-chain messages are identified, providing a comprehensive view of weekly protocol adoption and usage patterns.

## 2. Data sources

- **Blockchain events**: `send` function calls from `EndpointV1` and `EndpointV2` contracts, `PacketDelivered` events from `ReceiveUln301` and `EndpointV2` contracts, `SendToChain`, `OFTReceived`, and `OFTSent` events from `OFT` contracts, and `Swap` events from `StargateV1` contracts, covering Ethereum, Arbitrum, Avalanche, Base, and 26 other chains

## 3. Step-by-step calculation

### Component A: LayerZero user activity extraction

- **Purpose**: Identification of all users who interact with LayerZero protocols through function calls and events across multiple chains.
- **Logic**: User addresses are extracted from two primary sources: endpoint function calls that capture transaction initiators, and protocol events that capture both senders and receivers. For function calls, `send` function calls from both LayerZero V1 and LayerZero V2 endpoint contracts are processed, and the `from_address` parameter is extracted as the transaction sender. For events, multiple event types are processed, including `PacketDelivered` events from `ReceiveUln301` and `EndpointV2` contracts where the `receiver` parameter is identified, `OFTSent` events where the `fromAddress` parameter is captured, `OFTReceived` events where the `toAddress` parameter is captured, `SendToChain` events from `OFT` contracts where the `from` parameter is captured, and `Swap` events from `StargateV1` contracts where the `from` parameter is captured. Each interaction is tagged with the originating blockchain network, protocol version, and classified by user type as either "Transaction sender" or "Transaction receiver".
- **Key fields**: `block_timestamp`, `user_address`, `chain`, `user_type`, `product_id`, `version`, `transaction_hash`

### Component B: User activity aggregation and deduplication

- **Purpose**: Aggregation of user addresses per 7-day window and preparation for distinct counting.
- **Logic**: The extracted user activity data is transformed by truncating timestamps to weekly granularity to establish consistent weekly boundaries. The data is grouped by week, chain, user type, and product identifier while maintaining the individual user addresses. All relevant metadata, including chain information, user classification, and product differentiation, is preserved to enable detailed analysis while preparing for the final distinct count operation.
- **Key fields**: `timestamp`, `chain`, `user_type`, `product_id`, `user_address`

### Component C: Final aggregation and filtering

- **Purpose**: Final distinct count of active users and application of data quality filters.
- **Logic**: The user activity data is aggregated without additional joins, as all necessary user identification and classification is already performed. Weekly boundaries are established by truncating blockchain timestamps to the week level, ensuring consistent weekly reporting periods. A distinct count operation is applied to the `user_address` field within each weekly time bucket, effectively counting unique wallet addresses that interacted with LayerZero protocols once per 7-day window. Chain availability filtering is applied as a final step to ensure only reliable data is included in the final active users (weekly) counts.
- **Key fields**: `timestamp`, `chain`, `user_type`, `product_id`, `user_address`

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

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

LayerZeroZRO

Active users (weekly)

Active users (weekly)

Competitive landscape

Chain breakdown