Bridges

A bridge moves value from one chain to another. Each move leaves an event on the chain it departs from and another on the chain it arrives at, and facts_bridge_tokens.transfers pairs those two events into one row. One transfer belongs to two chains, so each side is keyed on its own column: filter source_chain_id = 'ethereum' for transfers leaving Ethereum, destination_chain_id = 'ethereum' for transfers arriving, or either for every transfer that touched the chain. Every row has a full pair of columns for each side: chain, transaction hash, block, sender, recipient, token address and amount, prefixed source_ or destination_. A transfer matched on one side only still appears, with the leg it has and an unmatched_reason saying why the other side stayed unmatched. To count matched pairs alone, require both chain columns to be present. Every column is documented at Bridges ▸ Transfers, including how an unmatched leg is recorded.

Sample queries

For any sum of value, use transfer_amount_usd: it prices the transfer once. source_transfer_amount_usd and destination_transfer_amount_usd price each leg on its own chain, and adding them counts one transfer twice; reach for them only when the question is the difference between the two ends.

The table splits by day on block_timestamp. Bound that column in every query; without a bound the query reads the whole table. For a daily total per token, metrics_bridge_tokens.source_transfer_volume_daily and metrics_bridge_tokens.destination_transfer_volume_daily answer the same question at a fraction of the cost.

Daily in and out
Where value went
By bridge

Compare the value leaving Ethereum with the value arriving each day. Testing the source and destination columns separately inside the sum splits the same measure into the two directions.

select
    timestamp_trunc(block_timestamp, day) as day,
    sum(if(source_chain_id = 'ethereum', transfer_amount_usd, 0)) as leaving_usd,
    sum(if(destination_chain_id = 'ethereum', transfer_amount_usd, 0)) as arriving_usd
from `facts_bridge_tokens.transfers`
where block_timestamp >= timestamp('2026-08-16')
  and block_timestamp < timestamp('2026-08-23')
  and (source_chain_id = 'ethereum' or destination_chain_id = 'ethereum')
group by day
order by day

Find where the value leaving Ethereum went.

select
    destination_chain_id,
    count(*) as transfers,
    sum(transfer_amount_usd) as volume_usd
from `facts_bridge_tokens.transfers`
where block_timestamp >= timestamp('2026-08-16')
  and block_timestamp < timestamp('2026-08-23')
  and source_chain_id = 'ethereum'
group by destination_chain_id
order by volume_usd desc
limit 20

Rank the bridges by the Ethereum value they moved. app_id names the bridge behind the transfer.

select
    apps.name,
    countif(transfers.source_chain_id = 'ethereum') as leaving,
    countif(transfers.destination_chain_id = 'ethereum') as arriving,
    sum(transfers.transfer_amount_usd) as volume_usd
from `facts_bridge_tokens.transfers` as transfers
join `dimensions.apps` as apps
    using (app_id)
where transfers.block_timestamp >= timestamp('2026-08-16')
  and transfers.block_timestamp < timestamp('2026-08-23')
  and (transfers.source_chain_id = 'ethereum' or transfers.destination_chain_id = 'ethereum')
group by apps.name
order by volume_usd desc

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Sample queries

​Sample queries

Sample queries