# Stargate Transfer volume Methodology

## 1. Overview

Transfer volume for Stargate measures the total value of assets moved across different blockchains using the Stargate protocol infrastructure. This metric serves as a primary indicator of bridge utilization and liquidity flow, which directly correlates with the protocol's ability to generate fees from cross-chain activity. Stargate utilizes both LayerZero V1 and LayerZero V2 messaging layers to facilitate these transfers.

## 2. Data sources

- **Blockchain events**: `SendToChain` and `Swap` events from `Stargate V1` contracts, `OFTReceived` events from `OFT` contracts, `PacketDelivered` events from `Endpoint V2` contracts, `BusDriven` events from `StargateTokenMessaging` contracts, and `Fill` events from `AoriSettlement` contracts, covering Ethereum, Arbitrum, Avalanche, Polygon, and 16 other chains
- **External data**: End-of-day price feeds and asset metadata

## 3. Step-by-step calculation

### Component A: Stargate V1 transfer extraction

- **Purpose**: Captures historical and ongoing bridging activity through the Stargate V1 architecture.
- **Logic**: `SendToChain` and `Swap` events are parsed from `Stargate V1` contracts. Asset quantities are extracted from the quantity or amount fields depending on the specific contract version. These events are associated with the LayerZero V1 messaging protocol.
- **Key fields**: `in_qty`, `in_amount`, `in_amountSD`, and `token_address`

### Component B: Stargate V2 bus-driven transfers

- **Purpose**: Identifies cross-chain transfers moving through the Stargate V2 messaging system.
- **Logic**: `OFTReceived` events from `OFT` contracts are filtered to ensure they correspond to confirmed deliveries. This is verified by matching the unique message identifiers against `PacketDelivered` events from `Endpoint V2` contracts and `BusDriven` events from `StargateTokenMessaging` contracts. This validation ensures that only finalized cross-chain movements are recorded.
- **Key fields**: `in_amountReceivedLD`, `in_guid`, and `token_address`

### Component C: Stargate fast swap volume

- **Purpose**: Accounts for volume generated through the Stargate fast swap settlement mechanism.
- **Logic**: `Fill` events are parsed from `AoriSettlement` contracts. The output token address and amount are extracted from the order details. In instances where the output involves native gas assets, the address is mapped to the corresponding wrapped gas asset for the respective chain to ensure accurate valuation.
- **Key fields**: `outputToken`, `outputAmount`, and `transaction_hash`

### Component D: Asset mapping and USD conversion

- **Purpose**: Normalizes all transfer activity into a standard USD value for aggregation.
- **Logic**: All extracted asset amounts are normalized by decimal precision using asset metadata. For assets issued as Omnichain Fungible Tokens (OFTs), the OFT contract addresses are mapped to their underlying asset addresses. These normalized amounts are multiplied by end-of-day asset prices. Volume is attributed to the source chain and aggregated at a daily granularity using UTC boundaries.
- **Key fields**: `underlying_token_address`, `amount_sent`, and `price_usd`

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

Total value of assets moved across chains through a bridge.

Transfer volume

Bridges

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.

Stargate

Transfer volume

Transfer volume

Chain breakdown