# chainlink Revenue Methodology

## 1. Overview

Chainlink revenue represents the total USD value of fees collected by the Chainlink protocol from two main sources: Cross-Chain Interoperability Protocol (CCIP) transaction fees and payment aggregator distributions. The protocol's ability to generate revenue from its cross-chain infrastructure services and oracle network operations is measured by this metric. Daily fee revenues are aggregated across multiple blockchain networks, converted to USD, and normalized by decimal precision to provide a comprehensive view of Chainlink's revenue generation.

## 2. Data sources

- **Blockchain events**: `CCIPSendRequested` events from `EVM2EVMOnRamp` contracts, `OnRampSet` events from `Router` and `RouterV2` contracts, and ERC-20 `Transfer` events for the LINK asset, covering Ethereum, Arbitrum, Avalanche, Monad, and 4 other chains
- **External data**: End-of-day asset price feeds for USD conversion across all supported assets
- **Asset metadata**: Asset decimal information for proper amount normalization

## 3. Step-by-step calculation

### Component A: Cross-Chain Interoperability Protocol (CCIP) cross-chain transaction fees

- **Purpose**: Captures revenue from users paying fees for cross-chain message and asset transfers via Chainlink's Cross-Chain Interoperability Protocol (CCIP) infrastructure
- **Logic**: All `CCIPSendRequested` events are extracted from `EVM2EVMOnRamp` contracts across eight supported chains. Each event contains the fee asset address and fee amount paid by the user. Non-removed events are filtered, and the `feeToken` and `feeTokenAmount` fields are extracted from the message data. Events are classified under the "Interoperability" business line with "infrastructure" market sector and "other" business segment categorization.
- **Key fields**: `block_timestamp` for daily aggregation, `feeToken` for the asset used to pay fees, `feeTokenAmount` for the raw fee amount, and contract `address` for account identification

### Component B: Cross-chain route mapping

- **Purpose**: Enriches Cross-Chain Interoperability Protocol (CCIP) fees with source-destination chain information to provide routing context
- **Logic**: Cross-Chain Interoperability Protocol (CCIP) fee events are joined with router configuration data from `OnRampSet` events. Mappings between OnRamp contract addresses and destination chain selectors are established by these router events. A lookup table of chain selector IDs to chain names is maintained to provide destination chain attribution. Routes are formatted as "Source - Destination" pairs, with unmapped destinations labeled as "Other".
- **Key fields**: `account_address` for joining with fee events, `chain` representing the source network, and derived `cross_chain_route` field combining source and destination chain names

### Component C: Payment aggregator revenues

- **Purpose**: Captures LINK asset distributions from Chainlink's payment aggregator to protocol treasury and staking rewards
- **Logic**: ERC-20 `Transfer` events of the LINK asset on Ethereum from the payment aggregator contract address to two specific recipient addresses—the Chainlink reserve address and the staking rewards address—are monitored. Only transfers of the official LINK asset contract are included, representing revenue flows from oracle services and other protocol operations back to the protocol treasury and node operator rewards.
- **Key fields**: `block_timestamp` for timing, `token_address` confirming LINK asset, `value` for transfer amount, `from_address` and `to_address` for validation

### Component D: Asset address standardization

- **Purpose**: Handles LINK assets on different chains that lack price feed coverage
- **Logic**: Special mapping logic is applied for LINK assets on Polygon and BSC networks. Since price feeds are missing for LINK on these chains, these asset addresses are mapped to the Ethereum LINK asset address for price conversion purposes. The original chain information is preserved separately to maintain proper attribution while enabling accurate USD conversion.
- **Key fields**: `token_address` remapped to Ethereum LINK address, `real_token_address` preserving original asset, `chain_id` adjusted for price lookup, `real_chain` preserving original chain

### Component E: Final aggregation and USD conversion

- **Purpose**: Combine all revenue components and normalize to USD for reporting
- **Logic**: All revenue components are combined using a union operation. Revenue amounts are converted to USD using end-of-day asset price feeds, with special handling for LINK assets on Polygon and BSC that use Ethereum LINK prices. Asset amounts are normalized by decimal precision using asset metadata. A finalization process is applied that validates dimensional IDs, fills date gaps with zero values, and filters results based on chain availability to produce the final daily revenue metric.
- **Key fields**: `timestamp` for daily granularity, `revenue` in USD, `chain_id` for network attribution

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

Revenue

Chainlink

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.

ChainlinkLINK

Revenue

Revenue

Competitive landscape

Chain breakdown