# Chainlink CCIP Tracker: Cross-Chain Messages and Token Transfers

> Chainlink CCIP activity by lane: cross-chain messages, token value moved, delivery times, fees paid in LINK or other tokens and token pool rate limits.

Markdown copy of https://voltfincrypto.com/apps/chainlink-ccip-tracker

**Question:** How many messages and how much token value move over Chainlink CCIP, on which lanes and how fast are they delivered?

- Kind: Dashboard in Voltfin Vantage
- Topic: [Layer 1 chains](https://voltfincrypto.com/topics/chains)
- Chains: Multi-chain, Ethereum, Arbitrum, Base, OP Mainnet, Avalanche, BNB Chain, Polygon
- Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is.

Chainlink's Cross-Chain Interoperability Protocol, CCIP, carries messages and tokens between chains. A message leaves through the source chain's OnRamp, a committing oracle network posts a Merkle root of messages to the destination, a separate Risk Management Network checks it and an executing network delivers it through the OffRamp. This dashboard follows each message from send to delivery.

Tokens move through token pools that either lock and release a token or burn and mint it, and each pool sets rate limits per lane that cap how much can cross in a window. Under the Cross-Chain Token standard, issuers deploy and control their own pools. The dashboard shows the value moving on each lane, which tokens use which pool type and how much capacity each lane has left.

## Blueprint

### Lanes

Messages and token value by lane, with delivery times.

- **Messages delivered** (count): CCIP messages executed on covered destination chains over the selected period.
- **Token value moved** (USD): Token value carried by those messages, valued at oracle prices at the send block.
- **Active lanes** (count): Source and destination pairs with at least one delivered message in the period.
- **Median delivery time** (minutes): The median time from send block to execution block across messages in the period.
- **Messages by day and source chain** (count): CCIP messages sent each day, split by source chain.
- **Busiest lanes**: Each lane's messages, token value, median delivery time and the share of fees paid in LINK over the period.

### Tokens and limits

Which tokens cross over CCIP, through which pools and how much capacity each lane has left.

- **Tokens with CCIP pools** (count): Tokens with at least one registered CCIP token pool on covered chains.
- **Lanes near their rate limit** (count): Token pool lanes whose available capacity is below a fifth of their maximum at the latest block.
- **Value by pool type** (USD): Token value moved in the period through lock-and-release pools and through burn-and-mint pools.
- **Tokens and their pools**: Each token's pool type, chains, rate limit per lane, capacity left now and value moved in the period.

Filters: Lane (Every covered source and destination pair); Period (Last 7, 30 or 90 days).

## How it will be measured

- Messages are decoded from each chain's CCIP OnRamp send events and matched by message id to their execution on the destination OffRamp, so a message counts once and its delivery time is the gap between the two blocks.
- Token transfers are the token amounts carried in each message, valued at oracle prices at the send block, and split by the pool's mechanism: lock and release, or burn and mint.
- Fees are read from each message's fee token and fee amount, so the split between LINK and other fee tokens is measured, not assumed.
- Rate limits are read from each token pool's inbound and outbound buckets for every lane at the latest block: capacity, refill rate and tokens available now.

## Data it needs

- `bridge_flows_daily` (to build): Deposits into and withdrawals out of canonical and major third-party bridges by chain, token and day, plus escrow balances at day end.
- `token_supply_daily` (to build): Total supply of each registry token on each chain at day end: wrapped BTC, liquid staking tokens, tokenized assets and other tracked tokens.
- `native_prices_daily` (to build): Reference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
- `address_labels` (to build): Labels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- Source: CCIP OnRamp send events on each covered chain: message id, sender, receiver, tokens, fee token and fee
- Source: OffRamp execution state events on each destination chain, matched by message id
- Source: Token pool rate limiter state per lane: capacity, rate and tokens available, read at the latest block
- Source: Token pool types and the tokens registered to each, from the CCIP token admin registry

## Questions

### What is Chainlink CCIP?

A protocol for sending messages, tokens or both between blockchains, run by Chainlink oracle networks. An app calls the CCIP router on the source chain and pays a fee, and the message or tokens arrive on the destination chain, where a receiver contract can act on them.

### How does CCIP verify a message?

A committing oracle network posts a Merkle root of messages from the source chain to the destination. A separate Risk Management Network, built and run independently, checks that root, and only then can an executing network deliver the messages against it. A message that fails either check is not executed.

### What is the Cross-Chain Token standard?

A way for token issuers to make their token transferable over CCIP on their own terms: they deploy a token pool on each chain, choose lock and release or burn and mint and keep control of the pools and their rate limits.

### What are CCIP rate limits?

Caps set per token pool and per lane on how much of a token can leave or arrive in a window. Each works like a bucket that refills over time, so a sudden drain through one lane is limited even if something else fails.

### How long does a CCIP transfer take?

CCIP waits for the source chain to reach finality before a message is committed, so delivery time depends mostly on the source chain. The dashboard shows the median per lane, measured from the send block to the execution block.

## Glossary

- **Lane**: A source and destination chain pair that CCIP connects; messages and rate limits are counted per lane.
- **Token pool**: The contract that locks and releases, or burns and mints, a token when it crosses chains over CCIP.
- **Risk Management Network**: An independent set of nodes that checks the messages CCIP commits and must approve them before they are executed.

## Related apps

- [Chainlink Price Feeds: Update Times, Heartbeats and Deviation](https://voltfincrypto.com/apps/chainlink-price-feeds)
- [LayerZero DVN Checker: Bridge Verifier Settings](https://voltfincrypto.com/apps/layerzero-dvn-checker)
- [Bridged Token Backing: Locked vs Minted Supply](https://voltfincrypto.com/apps/bridged-token-backing)
- [Wormhole Bridge Tracker: Messages, Token Transfers and NTT](https://voltfincrypto.com/apps/wormhole-bridge-tracker)
- [Hyperlane Tracker: Interchain Messages, Warp Routes and ISMs](https://voltfincrypto.com/apps/hyperlane-messages-warp-routes)
- [Blockchain Revenue Rankings: Monthly League Table](https://voltfincrypto.com/apps/blockchain-revenue-rankings)

Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F