> ## Documentation Index
> Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Bridges

> Every cross-chain transfer: matched legs, USD value and daily volume, across every bridge.

A bridge moves a token from one chain to another. The move leaves two events behind, one on each chain, and the catalog pairs them into a single transfer. `facts.bridge_transfers` holds those transfers for LayerZero v1 and v2, Circle CCTP v1 and v2, and Chainlink CCIP. The daily table totals them up per token.

## Pages

<CardGroup cols={2}>
  <Card title="Registry" icon="table-list" href="/docs/catalog/bridges/registry">
    Bridge identity, carried on the transfers table itself.
  </Card>

  <Card title="Transfers" icon="bolt" href="/docs/catalog/bridges/transfers">
    Every transfer, with the sending and arriving sides matched.
  </Card>

  <Card title="Metrics" icon="chart-line" href="/docs/catalog/bridges/metrics">
    Daily volume leaving and volume arriving, per token.
  </Card>
</CardGroup>

## What one row means

Most of the catalog has something you trade in the middle: a pool, a perpetual market, an order book. A bridge has nothing like that. There is only the token being moved and the bridge moving it, so bridge figures are published per token rather than per market. `metrics.bridge_tokens_daily` uses the token identifier that already exists in `dimensions.tokens` and adds no new list of its own.

Every transfer has a sending side and an arriving side, and we value both. Per token, you get the two sides separately: `source_transfer_volume` for the money leaving and `destination_transfer_volume` for the same money arriving. They describe one set of transfers from opposite ends, so adding the two columns counts the same money twice. When the question needs each transfer counted once, count it from [Transfers](/docs/catalog/bridges/transfers).