# Cross-Chain Interoperabilty Protocol (CCIP) Transfer volume Methodology

## 1. Overview

Transfer volume measures the total value of assets moved across different blockchains using the Cross-Chain Interoperabilty Protocol (CCIP). As an infrastructure-level metric, it tracks the economic throughput of the protocol's bridging and messaging capabilities. Since users pay fees to secure cross-chain transfers, this volume serves as a primary indicator of the project's capacity to generate fees and protocol revenue from cross-chain activity.

## 2. Data sources

- **Blockchain events**: `CCIPSendRequested` events from `EVM2EVMOnRamp`, `EVM2EVMOnRampV2`, and various `EVM2EVMOnRampPreLaunch` contracts, `CCIPMessageSent` events from `OnRampV3` and `OnRampCCIP2` contracts, `OnRampSet` events from `Router`, `RouterV2`, and various `RouterPreLaunch` contracts, and `CcipSend` instructions from `CcipRouter` programs, covering Ethereum, Arbitrum, Avalanche, Base, and 19 other chains
- **External data**: End-of-day price feeds and asset metadata

## 3. Step-by-step calculation

### Component A: Cross-chain route mapping

- **Purpose**: Establishes the relationship between protocol accounts and their respective destination chains.
- **Logic**: `OnRampSet` events are parsed from `Router`, `RouterV2`, and various `RouterPreLaunch` contracts. The `onRamp` address and `destChainSelector` are extracted to map specific contract accounts to their target destination chains. This mapping allows for the identification of cross-chain routes (e.g., Ethereum to Polygon) for all subsequent transfer activity.
- **Key fields**: `onRamp`, `destChainSelector`

### Component B: Cross-chain transfer extraction

- **Purpose**: Captures individual asset transfer details for every cross-chain request.
- **Logic**: `CCIPSendRequested` events are parsed from all versions of the `EVM2EVMOnRamp` contracts, `CCIPMessageSent` events are parsed from `OnRampV3` and `OnRampCCIP2` contracts, and `CcipSend` instructions are parsed from `CcipRouter` programs on Solana. Within `EVM2EVMOnRamp` and `OnRampV3` events, the `tokenAmounts` array is unnested to extract the specific quantity for each transfer. For `OnRampCCIP2` events, the asset address and amount are decoded from the binary encoded message. For Solana instructions, the asset address and amount are extracted from the asset amounts array. For standard transfers, the asset address is extracted directly; for V1.6.0 transfers, the asset address is resolved via a lookup of asset pool mappings. Destination chains are resolved either via route mapping from Component A or directly from the destination chain selector in the event or instruction data.
- **Key fields**: `token_address`, `sourcePoolAddress`, `amount`, `encodedMessage`, `destination_chain_selector`

### Component C: Asset adjustment and USD normalization

- **Purpose**: Corrects for specific asset implementation details and converts quantities to a unified USD value.
- **Logic**: Specific adjustments are applied to assets where direct price feeds are unavailable or require mapping to underlying liquidity. LINK transfers on Polygon and BSC are mapped to Ethereum-based LINK addresses for pricing. Additionally, `snxUSD` on Ethereum and Optimism is mapped to equivalent stablecoin feeds for valuation. All amounts are then normalized by decimal precision and multiplied by end-of-day price feeds.
- **Key fields**: `token_address`, `amount`, `timestamp`

### Component D: Final aggregation and filtering

- **Purpose**: Consolidates the processed data into daily totals per chain and product.
- **Logic**: The normalized USD values are aggregated by day, chain, and product ID. A zero-fill strategy is applied to ensure daily continuity, and a chain availability filter is utilized to ensure data is only displayed for periods with verified indexing freshness.
- **Key fields**: `transfer_volume`, `product_id`, `chain_id`

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

Total value of assets moved across chains through a bridge.

Transfer volume

Infrastructure

In order to bring determinism to the oracle layer, Chainlink has developed a network of decentralized oracle networks (DONs), with each DON involving a combination of multiple security techniques needed to service a particular use case.
The Chainlink stack supports multiple open standards for designing and operating oracle services, which currently span four key verticals: 1) Data, 2) Interoperability, 3) Compliance, and 4) Privacy. Built upon these standards exists an ever-expanding collection of modular, purpose-built oracle services, which can be easily created and seamlessly composed using the Chainlink Runtime Environment (CRE). CRE is a developer platform and decentralized execution environment for running, managing, and composing oracle services into scalable end-to-end solutions, which run in a highly secure, reliable, and cryptographically verifiable manner.

Chainlink is the industry-standard oracle platform bringing the capital markets onchain and powering the majority of decentralized finance (DeFi). The Chainlink stack provides the essential data, interoperability, compliance, and privacy standards needed to power advanced blockchain use cases for institutional tokenized assets, lending, payments, stablecoins, and more. Since inventing decentralized oracle networks, Chainlink has enabled tens of trillions in transaction value and now secures the vast majority of DeFi. 
Many of the world’s largest financial services institutions have also adopted Chainlink’s standards and infrastructure, including Swift, Euroclear, Mastercard, Fidelity International, UBS, ANZ, and top protocols such as Aave, GMX, Lido, and many others. Chainlink leverages a novel fee model where offchain and onchain revenue from enterprise adoption is converted to LINK tokens and stored in a strategic Chainlink Reserve. Learn more at chain.link.

Chainlink is not a governance protocol. Chainlink is an open-sourced platform of standards developers leverage to build next-generation onchain applications. It is developed and maintained by Chainlink Labs and a broader community of contributors. While there is no onchain token-based governance like in some DeFi protocols, the direction of the protocol is guided by core developers, researchers, and ecosystem partners, with feedback from the community.

Cross-Chain Interoperabilty Protocol (CCIP)

Transfer volume

Transfer volume

Chain breakdown