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
Registry
Bridge identity, carried on the transfers table itself.
Transfers
Every transfer, with the sending and arriving sides matched.
Metrics
Daily volume leaving and volume arriving, per token.
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.