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_transfers pairs those two events into one row. The table has no single chain_id column, because one transfer belongs to two chains: filter source_chain_id = 'plasma' for transfers leaving Plasma, destination_chain_id = 'plasma' for transfers arriving, or either for every transfer that touched the chain. Every column is documented at Bridges ▸ Transfers, including how an unmatched leg is recorded.

Sample queries

The table splits by day on block_timestamp. Bound that column in every query; without a bound the query reads the whole table.

Daily in and out
Where value went
By bridge

Compare the value leaving Plasma 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 = 'plasma', transfer_amount_usd, 0)) as leaving_usd,
    sum(if(destination_chain_id = 'plasma', transfer_amount_usd, 0)) as arriving_usd
from `facts.bridge_transfers`
where block_timestamp >= timestamp('2026-08-16')
  and block_timestamp < timestamp('2026-08-23')
  and (source_chain_id = 'plasma' or destination_chain_id = 'plasma')
group by day
order by day

Find where the value leaving Plasma went.

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

Rank the bridges by the Plasma value they carried. app_id names the bridge that carried the transfer.

select
    apps.name,
    countif(transfers.source_chain_id = 'plasma') as leaving,
    countif(transfers.destination_chain_id = 'plasma') as arriving,
    sum(transfers.transfer_amount_usd) as volume_usd
from `facts.bridge_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 = 'plasma' or transfers.destination_chain_id = 'plasma')
group by apps.name
order by volume_usd desc

Notes

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. Every row holds a full pair of columns for each side: chain, transaction hash, block, sender, recipient, token address and amount, prefixed source_ or destination_. Some rows have only one leg: a transfer whose other side was never found still appears, carrying the leg it has, with unmatched_reason saying why the other is missing. Counting only matched pairs means requiring both chain columns to be present. For daily totals, metrics.bridge_tokens_daily carries the answer per token at a fraction of the cost.

Overview

Core entities

Market verticals

Chain verticals

Sample queries

Notes

​Sample queries

​Notes

Sample queries

Notes