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

## 1. Overview

Transfer volume measures the total USD value of assets moved across chains using the LayerZero protocol. Cross-chain transfer activity is captured across LayerZero V1 and LayerZero V2, including regular OFT transfers, Stargate bridge transfers, and FastSwap volumes. Transfer amounts from multiple LayerZero products are aggregated and converted to USD using end-of-day price feeds, providing a comprehensive view of value flowing through the LayerZero ecosystem.

## 2. Data sources

- **Blockchain events**: `OFTSent`, `SendToChain`, and `OFTReceived` events from `OFT` contracts, `SendToChain` and `Swap` events from `StargateV1` contracts, `PacketSent` and `PacketDelivered` events from `EndpointV2` contracts, `BusDriven` events from `StargateTokenMessaging` contracts, and `Fill` events from `AoriSettlement` contracts, plus `send` function calls from `EndpointV1` and `EndpointV2` contracts, covering Ethereum, Arbitrum, Base, BSC, and 25 other chains
- **External data**: End-of-day asset price feeds, asset metadata, and state call results mapping OFT asset addresses to underlying asset addresses

## 3. Step-by-step calculation

### Component A: LayerZero protocol transfers

- **Purpose**: Captures transfer volumes from LayerZero V1 and LayerZero V2 OFT transfers across all supported chains
- **Logic**: Transfer events are extracted from multiple LayerZero contract types. For LayerZero V2 on active chains, `OFTSent` events are collected and validated against `send` function calls from `EndpointV2` contracts. For LayerZero V2 on expansion chains where the `send` function is not decoded, `OFTSent` events are validated by verifying the existence of a corresponding `PacketSent` event from `EndpointV2` contracts within the same transaction and block timestamp. For LayerZero V1, `SendToChain` events from `OFT` contracts, `SendToChain` events from `StargateV1` contracts, and `Swap` events from `StargateV1` contracts are combined and validated against `send` function calls from `EndpointV1` contracts. OFT asset addresses are mapped to underlying asset addresses using state call results, with native asset cases handled by substituting wrapped gas assets for each chain.
- **Key fields**: `amount_sent` for transfer amounts, `token_address` for asset identification, `chain` for source chain attribution

### Component B: Stargate bridge transfers

- **Purpose**: Captures cross-chain transfer volumes through the Stargate V2 bridge protocol
- **Logic**: Completed cross-chain transfers are identified by joining `BusDriven` events from `StargateTokenMessaging` contracts with `OFTReceived` events from `OFT` contracts on destination chains, which are validated against `PacketDelivered` events from `EndpointV2` contracts. The `guid` field is used to link bus-driven events to actual receipt events. Destination chain transfers are mapped back to source chains for proper attribution. OFT to underlying asset mapping is applied using state call results.
- **Key fields**: `amount_sent` for received amounts, `guid` for cross-chain transaction linking, `source_chain` for proper chain attribution

### Component C: FastSwap volume

- **Purpose**: Captures trading volume from Stargate's FastSwap feature across supported chains
- **Logic**: Volume is extracted from `Fill` events from `AoriSettlement` contracts, specifically using the output amount from the order structure. Native asset representation is handled by mapping the special address `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` to wrapped gas assets based on chain-specific mappings. All FastSwap volume is tagged with the `Stargate` product identifier.
- **Key fields**: `volume` for swap volume, `token_address` for asset identification

### Component D: USD conversion and aggregation

- **Purpose**: Normalizes transfer volumes, converts them to USD, and aggregates them by source chain and product
- **Logic**: All transfer components are combined using union operations. Transfer amounts are normalized by decimal precision and converted to USD using end-of-day asset price feeds. Timestamps are truncated to daily boundaries. Volumes are summed by source chain and product type, with source chain attribution ensuring transfers are counted against the originating chain rather than the destination. Schema validation is applied, and any gaps in the time series are filled with zeros.
- **Key fields**: `timestamp`, `chain_id`, `product_id`, `transfer_volume`

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

Total value of assets moved across chains through a bridge.

LayerZeroZRO

Transfer volume

Transfer volume

Competitive landscape

Chain breakdown